view Side-By-Side changes

IPPM Working Group                                          S. Niccolini
Internet-Draft                                             S. Tartarelli
Intended status: Standards Track                              J. Quittek
Expires: August 26, 2007 February 25, 2008                                           NEC
                                                                M. Swany
                                                                    UDel
                                                       February 22,
                                                         August 24, 2007


      Traceroute Measurements


    Information Model and XML Data Model
                  draft-ietf-ippm-storetraceroutes-03 for Traceroute Measurements
                  draft-ietf-ippm-storetraceroutes-04

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   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 obsoleted 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.

   This Internet-Draft will expire on August 26, 2007. February 25, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This memo document describes a standard way to store traceroute measurements.
   To better address the traceroute measurements storing issue, configuration and
   the
   authors results of traceroute measurements.  This document first of all give a definition of the traceroute tool,
   describe
   describes the tool itself as well as its parameters and the default
   values on the most common operating systems and the output results



Niccolini, et al.        Expires August 26, 2007                [Page 1]

Internet-Draft          Traceroute Storage Format          February 2007


   that can be stored.  Afterwards, itself; 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



Niccolini, et al.       Expires February 25, 2008               [Page 1]

Internet-Draft          Traceroute Storage Format            August 2007


   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 based on XML is then proposed in order defined to
   actually store
   the results of traceroute measurements.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Definition of Traceroute . . . . .  Terminology used in this document  . . . . . . . . . . . . . .  3
     2.1.  Traceroute Configuration Parameters  . . . . . . . . . . .  4
   3.  Known Problems with  The Traceroute tool and its operations . . . . . . . . . . . . . . . .  8
     3.1.  Accuracy of  4
   4.  Results  . . . . . . . . . . . . . . . . . . .  8
     3.2.  Alternative of traceroute Implementations . . . . . . . . . .  8
   4.  Reports/results  . . . . . . . . . measurements . . . . . . . . . . . . . .  8  4
   5.  Information Model for Storing Traceroute Measurements  . . . .  9 . . . .  5
     5.1.  Data Types . . . . . . . . . . . . . . . . . . . . . . . .  9  6
     5.2.  Information Elements . . . . . . . . . . . . . . . . . . . 10  7
       5.2.1.  Configuration Information Elements . . . . . . . . . . 11  7
       5.2.2.  Results Information Elements . . . . . . . . . . . . . 15 11
       5.2.3.  Information Element Correlating Configuration and
               Results Elements . . . . . . . . . . . . . . . . . . . 18 15
       5.2.4.  Information Elements to compare traceroute
               measurements results one with each other . . . . . . . 15
   6.  Data Model for Storing Traceroute Measurements . . . . . . . . 19 16
   7.  XML Schema for traceroute Measurements . . . . . . . . . . . . 20 17
   8.  Differences to DISMAN-TRACEROUTE-MIB  Security Considerations  . . . . . . . . . . . . . 38
     8.1.  Naming . . . . . . 35
     8.1.  Conducting Traceroute Measurements . . . . . . . . . . . . 35
     8.2.  Securing Traceroute Measurements Information . . . . . . . 36
   9.  IANA Considerations  . 39
     8.2.  Semantics . . . . . . . . . . . . . . . . . . . . 36
   10. References . . . . . . 39
     8.3.  Additional Information Elements . . . . . . . . . . . . . 40
   9.  Security Considerations . . . . . . . 37
     10.1. Normative References . . . . . . . . . . . . 40
     9.1.  Conducting . . . . . . . 37
     10.2. Informative References . . . . . . . . . . . . . . . . . . 37
   Appendix A.  Traceroute Measurements Default Configuration Parameters . . . . . 38
     A.1.  Alternative Traceroute Implementations . . . . . . . 40
     9.2.  Securing . . . 42
   Appendix B.  Known Problems with Traceroute Measurement Results  . . . . . . . . . 41
   10. IANA Considerations . . 42
     B.1.  Compatibility between traceroute measurements results
           and IPPM metrics . . . . . . . . . . . . . . . . . . . . . 41
   11. References 42
   Appendix C.  Differences to DISMAN-TRACEROUTE-MIB  . . . . . . . . 43
     C.1.  Naming . . . . . . . . . . . . . . . . . . 42
     11.1. Normative References . . . . . . . . 44
     C.2.  Semantics  . . . . . . . . . . . . . . 42
     11.2. Informative References . . . . . . . . . . 44
     C.3.  Additional Information Elements  . . . . . . . . 42 . . . . . 45
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43 45
   Intellectual Property and Copyright Statements . . . . . . . . . . 45 47










Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 2]

Internet-Draft          Traceroute Storage Format          February            August 2007


1.  Introduction

   Traceroutes are being used by lots of measurement efforts, either as
   an independent measurement or to get path information to support
   other measurement efforts.  That is why there is the need to
   standardize the way traceroute measurements are stored and the
   related metrics associated with such measurements.  Since traceroute
   is a tool that has built-in configurable mechanisms like time-outs configuration and can experience problems related to the crossing results of firewalls thus
   experiencing fake losses or incomplete delay information. traceroute
   measurements are stored.  The standard metrics defined by IPPM
   working group in matter of delay, connectivity and losses do not
   apply to the metrics returned by the traceroute tool; therefore, in
   order to compare results of traceroute measurements, the solution only
   possibility is to add to the stored results a specification of the
   operating system and version for the tool used.
   Moreover there is a need to better define the traceroute tool as well
   as its parameters and the results it outputs since, to the authors'
   knowledge, there is so far no standard describing these.  These are
   the motivations that moved the authors to write this draft in the
   context of the IPPM working group even if other working groups (like
   DISMAN) have already addressed similar issues related to the
   definition of the MIB for configuring and retrieving traceroute
   measurements results. used.  This draft,
   document, in order to store traceroute results of traceroute measurements and
   allow comparison of them, defines a standard way to store
   traceroute measurements them using
   a XML schema.  The draft document is organised organized as follows: Section 2 gives
   defines the definition of traceroute terminology used as
   reference in this document, Section 3 describes
   the rest of traceroute tool, Section 4 describes the draft as well results of a traceroute
   measurement as displayed to the screen from which the traceroute
   configurable parameters and their default values for the most common
   operating systems.  Section 3 reports on both traceroute accuracy of
   results and existing alternatives for traceroute implementations.
   Section 4 describes the results available from the traceroute output
   screen. tool
   was launched.  Section 5 and Section 6 respectively describe our proposed
   Information the
   information model and Data data model for storing configuration and
   results of the traceroute measurements.
   Section 8 reports the differences to [RFC4560].  The draft document ends with
   security considerations and IANA considerations in Section 9 8 and
   Section 10 9 respectively.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119.


2.  Definition  Terminology used in this document

   The terminology used in this document is defined as follow:
   o  traceroute tool: a software tool for network diagnostic behaving
      like described in Section 3;
   o  traceroute measurement: an instance of the traceroute tool
      launched, with specific configuration parameters (traceroute
      measurement configuration parameters), from a specific host
      (initiator of the traceroute measurement) giving as output
      specific traceroute measurement results;
   o  traceroute probe: one of many IP packets send out by the
      traceroute tool during a traceroute measurement;
   o  traceroute measurement configuration parameters: the configuration
      parameters of a traceroute measurement;
   o  traceroute measurement results: the results of a traceroute
      measurement;
   o  traceroute measurement information: both the results and the
      configuration parameters of a traceroute measurement;




Niccolini, et al.       Expires February 25, 2008               [Page 3]

Internet-Draft          Traceroute Storage Format            August 2007


   o  traceroute measurement path: a sequence of hosts transited in
      order by traceroute probes during a traceroute measurement;


3.  The Traceroute tool and its operations

   Traceroute is a network diagnostic tool used to determine the hop by
   hop path from a source to a destination and the Round Trip Time (RTT)
   from the source to each hop.  Traceroute can therefore be therefore used to
   discover where and how a host is connected to some information (hop counts, delays, etc.) about the Internet path
   between the initiator of the traceroute measurement and can be



Niccolini, et al.        Expires August 26, 2007                [Page 3]

Internet-Draft          Traceroute Storage Format          February 2007


   usefully employed to troubleshoot network connections. other hosts.

   Typically, the traceroute attemps tool attempts to discover the path to a
   destination by sending UDP probes with specific time-to-live (TTL)
   values in the IP packet header and trying to elicit an ICMP
   TIME_EXCEEDED response from each gateway along the path to some host.

   More in detail, the host running the traceroute sends the a first set of probes with TTL equal to one 1 are sent by
   the traceroute tool from the host initiating the traceroute
   measurement (some tool implementations allow setting the initial TTL
   to a value equal to "n" different from one, 1, so that the first "n-1"
   hops are skipped and the first hop that will be traced is the "n-th"
   in the path).  Upon receiving a probe, the first hop host decreases
   the TTL value by one.  By observing a TTL value equal to zero, the
   host rejects the probe and typically returns an ICMP message with a
   TIME_EXCEEDED value.  Traceroute  The traceroute tool can therefore derive the IP
   address of the first hop from the header of the ICMP message and
   evaluate the RTT between the source host initiating the traceroute
   measurement and the first hop.  The next hops are discovered
   following the same procedure, taking care of increasing at each step
   the TTL value of the outgoing probes by one.  The TTL value is increased until
   either an ICMP PORT_UNREACHABLE message is received, meaning that the
   destination host has been reached, or the maximum configured number
   of hops has been hit.

   Some implementations, use ICMP Echos, instead of UDP datagrams.
   However, many routers do not return ICMP messages about ICMP
   messages, i.e. no ICMP TIME_EXCEEDED is returned for an ICMP Echo.
   Therefore, in this draft we RECOMMEND document recommends to base implementations on UDP
   datagrams.

2.1.  Traceroute Configuration Parameters

   In order to define an information model for storing traceroutes, we
   first investigated which configuration parameters are relevant when
   running traceroute.  We considered four major traceroute
   implementations and compared them based on configurable parameters
   and default values.  The LINUX (SUSE 9.1), BSD (FreeBSD 7.0) and UNIX
   (SunOS 5.9) implemetations are based  Considerations on UDP datagrams, while the
   WINDOWS (XP SP2) one uses ICMP Echos.  The comparison is summarized
   in TCP-based implementations of the following table, where an N/A
   traceroute tool are reported in the option column, means that
   such parameter is not configurable for the specific implementation.
   A comprehensive comparison Appendix A.1.


4.  Results of available implementations is outside traceroute measurements

   The following list reports the scope of this draft; however, already information fields provided as results
   by sampling a few different
   implementations, we can observe that they can differ quite
   significantly in terms of configurable parameters and also default
   values.  Note that all traceroute tool implementations considered.  The order in the following table we reported only those
   options
   which they are available reported here is not relevant and it changes in at least two of the considered
   implementations.



Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 4]

Internet-Draft          Traceroute Storage Format          February            August 2007


             +---------------------------------------------------------+
             |  OS    |Option|           Description         | Default |
             +--------+------+-------------------------------+---------+
             | LINUX  | -m   |Specify


   different implementations.  For each hop the information reported is:
   o  the maximum TTL used   |   30    |
             |--------+------|in outgoing probes.            |---------|
             | FreeBSD| -m   |                               |  OS var |
             |--------+------|                               |---------|
             | UNIX   | -m   |                               |   30    |
             |--------+------|                               |---------|
             | WINDOWS| -h   |                               |   30    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -n   |Display hop addresses          |    -    |
             |--------+------|numerically rather than        |---------|
             | FreeBSD| -n   |simbolically.                  |    -    |
             |--------+------|                               |---------|
             | UNIX   | -n   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| -d   |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -w   |Set index;
   o  the time host symbolic address, provided that at least one of the
      probes received a response, the symbolic address could be resolved
      at the corresponding host and that the option to wait for display only
      numerical addresses was not set;
   o  the host IP address, provided that at least one of the probes
      received a     |  3 sec  |
             |--------+------|response response;
   o  the RTT for each response to a probe.           |---------|
             | FreeBSD| -w   |                               |  5 sec  |
             |--------+------|                               |---------|
             | UNIX   | -w   |                               |  5 sec  |
             |--------+------|                               |---------|
             | WINDOWS| -w   |                               |  4 sec  |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Specify a loose source route   |    -    |
             |--------+------|gateway (to direct
   Depending on the         |---------|
             | FreeBSD| -g   |traceroute through routers not |    -    |
             |--------+------|necessarily traceroute tool implementation, additional
   information might be displayed in the path).      |---------|
             | UNIX   | -g   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| -g   |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -p   |Set the base UDP port number   |  33434  |
             |------- +------|used in output (for instance MPLS-
   related information).

   It might happen that some probes                 |---------|
             | FreeBSD| -p   |(UDP port = base + nhops - 1). |  33434  |
             |--------+------|                               |---------|
             | UNIX   | -p   |                               |  33434  |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -q   |Set do not receive a response within the number of probes per   |    3    |
             |--------+------|TTL.                           |---------|
             | FreeBSD| -q   |                               |    3    |
             |--------+------|                               |---------|
             | UNIX   | -q   |                               |    3    |



Niccolini, et al.        Expires August 26, 2007                [Page 5]

Internet-Draft          Traceroute Storage Format          February 2007


             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    3    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -S   |Set
   configured time-out (for instance if the IP source address probe is filtered out by a
   firewall).  In this case, an "*" is displayed in   |IP       |
             |--------+------|outgoing probes to place of the         |address  |
             | FreeBSD| -s   |specified value.               |of RTT.
   The information model reflects this using a string with the   |
             |--------+------|                               |out      |
             | UNIX   | -s   |                               |interface|
             |--------+------|                               |         |
             | WINDOWS| N/A  |                               |         |
             +--------+------+-------------------------------+---------+
             | LINUX  | -t   |Set value of
   "RoundTripTimeNotAvailable" meaning either the type-of-service (TOS)  |    0    |
             |--------+------|in probe was lost because
   of a time-out or it was not possible to transmit a probe.  It may
   also happen that some implementations print the probes same line multiple
   times when a router decreases the TTL by more than one looking like
   multiple hops, the information model is not impacted by this since
   each line is handled separately and it is left to the specified |---------|
             | FreeBSD| -t   |value.                         | applications
   handling the XML file how to deal with it.  Moreover, for delays
   below 1 ms, some implementations reports 0    |
             |--------+------|                               |---------|
             | ms (e.g.  UNIX   | -t   |                               |    0    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    0    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -v   |Verbose output: received ICMP  |    -    |
             |--------+------|packets other than             |---------|
             | FreeBSD| -v   |TIME_EXCEEDED and              |    -    |
             |--------+------|UNREACHABLE are listed.        |---------|
             | UNIX   | -v   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               | LINUX)
   while WINDOWS tracert reports "< 1 ms".


5.  Information Model for Traceroute Measurements

   The information model is composed of information elements; for
   defining these information elements, a template is used.  Such
   template is specified in the list below:

   o  name -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Set A unique and meaningful name for the time (in msec) information element.
      The preferred spelling for the name is to     | use mixed case if the
      name is compound, with an initial lower case letter, e.g.,
      "sourceIpAddress".
   o  description -    |
             |--------+------|pause between probes.          |---------|
             | FreeBSD| -z   |                               |    0    |
             |--------+------|                               |---------|
             | UNIX   | -P   |                               |    0    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               | The semantics of this information element.
   o  dataType -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -r   |Bypass One of the normal routing      |    -    |
             |--------+------|tables and send directly types listed in Section 5.1 of this document
      or in an extension of the information model.  The type space for
      attributes is constrained to a  |---------|
             | FreeBSD| -r   |host on attached network.      |    -    |
             |--------+------|                               |---------|
             | UNIX   | -r   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               | facilitate implementation.
   o  units -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -f   |Set If the initial TTL element is a measure of some kind, the units
      identify what the measure is.
   o  default value - The default value for the    |    1    |
             |--------+------|first probe.                   |---------|
             | FreeBSD| -f   |                               |    1    |
             |--------+------|                               |---------|
             | UNIX   | -f   |                               |    1    | element (where
      applicable).





Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 6] 5]

Internet-Draft          Traceroute Storage Format          February            August 2007


             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    1    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -F   |Set


5.1.  Data Types

   This section describes the "don't fragment" bit.  |    -    |
             |--------+------|                               |---------|
             | FreeBSD| -F   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -F   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Enables socket level debugging.|    -    |
             |--------+------|                               |---------|
             | FreeBSD| -d   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -d   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Use ICMP ECHO instead set of UDP   |    -    |
             |--------+------|datagrams.                     |---------|
             | FreeBSD| -I   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -I   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               | valid data types of the information
   model.

   o  String -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -I   |Specify The type "String" represents a network interface to |    -    |
             |--------+------|obtain finite length string of
      valid characters from the IP address Unicode character encoding set.  Unicode
      allows for      |---------|
             | FreeBSD| -i   |outgoing IP packets            |    -    |
             |--------+------|(alternative ASCII and many other international character sets to option -s).    |---------|
             | UNIX   | -i   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               | be
      used.  It is expected that strings will be encoded in UTF-8
      format, which is identical in encoding for USASCII characters, but
      also accommodates other Unicode multi-byte characters.
   o  InetAddressType -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Toggle checksum.               |    -    |
             |--------+------|                               |---------|
             | FreeBSD| -x   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -x   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  |  -   |As optional last paramater,    |Depends  |
             |--------+------|LINUX, FreeBSD and UNIX        |on       |
             | FreeBSD|  -   |implementations allow          |implement|
             |--------+------|specifying the probe datagram  |ation.   |
             | UNIX   |  -   |length for outgoing probes.    |         |



Niccolini, et al.        Expires August 26, 2007                [Page 7]

Internet-Draft          Traceroute Storage Format          February 2007


             |--------+------|                               |         |
             | WINDOWS| N/A  |                               |         |
             +--------+------+-------------------------------+---------+


3.  Known Problems with Traceroute

3.1.  Accuracy The type "InetAddressType" represents a type of Results

   A known inconsistency exists between the round-trip delay metric
   defined by the IPPM working group and the results returned by the
   current traceroute implementations.  Unfortunately, it is unlikely
   that the traceroute implementations will implement the standard
   definition in the near future.  In order
      Internet address.  The allowed values are to compare results of
   different traceroute measurements, specifications both of the
   operating system (name and version) and of the traceroute tool
   version used be intended as
      imported from [RFC4001]; an additional allowed value is
      "asnumber".
   o  InetAddress - The type "InetAddress" denotes a generic Internet
      address.  The allowed values are added to be intended as imported from
      [RFC4001]; an additional allowed value is the metadata elements in order AS number to help in
   comparing metrics.  Moreover, be
      indicated as the traceroute has built-in
   configurable mechanisms like time-outs and can experience problems
   related to actual number plus the crossing of firewalls; therefore some of indication how the packets
   that traceroute sends out end up being time-out or filtered.  As mapping
      from IP address to AS number was performed.
   o  TruthValue - The type "TruthValue" represents a
   consequence, it might not be possible Boolean value.
      The allowed values are to trace be intended as imported from [RFC2579].
   o  Unsigned32 - The type "Unsigned32" represents a value in the path to range
      (0..4294967295).
   o  Unsigned16 - The type "Unsigned16" represents a node or
   there might not be value in the range
      (0..65535).
   o  Unsigned8 - The type "Unsigned32" represents a complete set value in the range
      (0..255).
   o  InterfaceIndexOrZero - The type "InterfaceIndexOrZero" is an
      extension of probes describing the RTT InterfaceIndex convention.  The latter defines a
      greater than zero value used to
   reach it.

3.2.  Alternative traceroute Implementations

   As stated above, identify an interface or interface
      sub-layer in the widespred use system.  This extension permits the additional
      value of firewalls zero.  Examples of the usage of zero might prevent UDP include
      situations where interface was unknown, or
   ICMP based traceroutes when none or all
      interfaces need to completely trace the path be referenced.  The allowed values are to be
      intended as imported from [RFC2863].
   o  ProbesType - The type "ProbesType" represents a destination,
   since way of indicating
      the protocol used for the traceroute probes might end up being filtered.  In some cases,
   such limitation might be overcome by sending instead TCP packets probes.  Allowed values are
      UDP, TCP, ICMP.
   o  DateAndTime - The type "DateAndTime" represents a date-time
      specification.  The allowed values are to
   specific ports be intended as imported
      from [RFC2579] apart from the fact that hosts located behind in this document there is
      the firewall are listening
   for connections on.  TCP based implementations use TCP SYN or FYN
   probes and listen for TIME_EXCEEDED messages, TCP RESET and other
   messages from firewalls and gateways on the path.  On the other hand,
   some firewalls filter out TCP SYN packets need to prevent denial of
   service attacks, therefore the actual advantage of using TCP use a millisecond resolution instead
   of UDP traceroute depends mainly on firewall configurations, which
   are not known in adavance.  A detailed analysis of TCP based
   traceroutes a decisecond one.
   o  OperationResponseStatus - The type "OperationResponseStatus" is outside the scope of this draft, therefore in the
   sequel, we will restrict our focus
      used to report the most commonly implemented
   UDP based traceroute.


4.  Reports/results

   The following list reports the information fields provided by all
   traceroute implementations considered. result of an operation.  The order in which they allowed values are
      to be intended as imported from [RFC4560].





Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 8] 6]

Internet-Draft          Traceroute Storage Format          February            August 2007


   reported here is not relevant and it changes in different
   implementations.  For each hop the information reported is:
   o


5.2.  Information Elements

   This section describes the hop index;
   o elements related to the host symbolical address, provided that at least one storing of the
      probes received a response, the symbolic address could be resolved
      at the correponding host
   traceroute measurement.  The elements are grouped in two groups
   (Configuration and that the option Results) according to display only
      numerical addresses was not set;
   o  the host IP address, provided that at least one their semantics.  In order
   to relate configuration and results elements by means of the probes
      received a response;
   o  the RTT for each response common
   unique identifier, an additional element is defined belonging to a probe.
   Depending on both
   the traceroute implementation, additional information
   might be displayed in the output (for instance MPLS-related
   information).

   It might happen that some probes do not receive a response within the
   configured time-out (for instance if the probe is filtered out by a
   firewall).  In this case, an "*" is displayed in place of the RTT.
   Besides, for delays below 1 ms, some implementations reports 0 ms
   (f.i.  UNIX and LINUX) while WINDOWS tracert reports "< 1 ms".


5. two groups.

5.2.1.  Configuration Information Model for Storing Traceroute Measurements Elements

   This section describes the information model for elements specific to the traceroute
   measurements data storing.  The information model is composed configuration of
   information elements; for defining these information elements, a
   template is used.  Such template is specified in
   the list below: traceroute measurement.

5.2.1.1.  CtlTargetAddressType

   o  name - A unique and meaningful name for the information element.
      The preferred spelling for the name is to use mixed case if the
      name is compound, with an initial lower case letter, e.g.,
      "sourceIpAddress". CtlTargetAddressType
   o  description - The semantics Specifies the type of this information element. destination address used in
      the traceroute measurement.
   o  dataType - One of InetAddressType
   o  units - N/A
   o  default value - N/A

5.2.1.2.  CtlTargetAddress

   o  name - CtlTargetAddress
   o  description - Specifies the types listed in Section 5.1 of this document
      or host address used in an extension of the information model. traceroute
      measurement.  The host address type space for
      attributes is constrained to facilitate implementation.
   o  units - If can be determined by the element is a measure
      examining the value of some kind, the corresponding CtlTargetAddressType.
   o  dataType - InetAddress
   o  units
      identify what the measure is. - N/A
   o  default value - The default value for the element (where
      applicable).

5.1.  Data Types

   This section describes N/A

5.2.1.3.  CtlBypassRouteTable

   o  name - CtlBypassRouteTable
   o  description - Specifies if the set of valid data types optional bypassing of the information
   model. route
      table was enabled or not.  If enabled, the normal routing tables
      will be bypassed and the probes will be sent directly to a host on
      an attached network.  If the host is not on a directly-attached
      network, an error is returned.  This option can be used to perform
      the traceroute measurement to a local host through an interface
      that has no route defined.
   o  dataType - TruthValue
   o  units - N/A
   o  default value - false





Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 9] 7]

Internet-Draft          Traceroute Storage Format          February            August 2007


5.2.1.4.  CtlProbeDataSize

   o  String  name - The type "String" represents a finite length string of
      valid characters from the Unicode character encoding set.  Unicode
      allows for ASCII and many other international character sets to be
      used.  It is expected that strings will be encoded in UTF-8
      format, which is identical in encoding for USASCII characters, but
      also accomodates other Unicode multibyte characters. CtlProbeDataSize
   o  InetAddressType  description - The type "InetAddressType" represents a type Specifies the size of the probes of
      Internet address.  The allowed values are to be intended as
      imported from [RFC4001]; an additional allowed value is
      "asnumber".
   o  InetAddress - The type "InetAddress" denotes a generic Internet
      address.  The allowed values traceroute
      measurement in octets.  If UDP datagrams are to be intended used as imported from
      [RFC4001]; an additional allowed probes, then
      the value contained in this object is the AS number exact.  If another protocol
      is used to be
      indicated as the actual number plus transmit probes (i.e.  TCP or ICMP) for which the indication how
      specified size is not appropriate, then the mapping
      from IP address to AS number was performed.
   o  TruthValue - The type "TruthValue" represents a boolean value.
      The allowed values are implementation can use
      whatever size (appropriate to be intended as imported from [RFC2579].
   o  Unsigned32 - The type "Unsigned32" represents a value in the range
      (0..4294967295).
   o  InterfaceIndexOrZero - The type "InterfaceIndexOrZero" method) is an
      extension of closest to the InterfaceIndex convention.
      specified size.  The latter defines a
      greater than zero maximum value used to identify an interface or interface
      sub-layer in the system.  This extension permits for this object was computed by
      subtracting the additional
      value of zero.  Examples smallest possible IP header size of 20 octets
      (IPv4 header with no options) and the usage UDP header size of zero might include
      situations where interface was unknown, or when none or all
      interfaces need to be referenced.  The allowed values are to be
      intended as imported 8 octets
      from [RFC2863].
   o  ProbesType - The type "ProbesType" represents the maximum IP packet size.  An IP packet has a way maximum size
      of indicating
      the protocol used for the traceroute probes.  Allowed values are
      UDP, TCP, ICMP. 65535 octets (excluding IPv6 Jumbograms).
   o  DateAndTime  dataType - The type "DateAndTime" represents a date-time
      specification.  The allowed values are to be intended as imported
      from [RFC2579] apart from Unsigned32
   o  units - octets
   o  default value - 0

5.2.1.5.  CtlTimeOut

   o  name - CtlTimeOut
   o  description - Specifies the fact that time-out value, in this document there is
      the need to use a milli-second resolution instead seconds, for each
      probe of a deci-second
      one. traceroute measurement.
   o  OperationResponseStatus  dataType - The type "OperationResponseStatus" is
      used to report Unsigned32
   o  units - seconds
   o  default value - 3

5.2.1.6.  CtlProbesPerHop

   o  name - CtlProbesPerHop
   o  description - Specifies the result number of an operation.  The allowed values probes with the same time-
      to-live (TTL) value that are
      to be intended as imported from [RFC4560].

5.2.  Information Elements

   This section describes sent for each host.
   o  dataType - Unsigned32
   o  units - probes
   o  default value - 3

5.2.1.7.  CtlPort

   o  name - CtlPort
   o  description - Specifies the elements of base UDP port used by the traceroute
      measurement.
   The elements are grouped  A port that is not in two groups (Configuration and Results)
   according to their semantics.  In order use at the destination
      (target) host needs to relate configuration and
   results elements by means of a common unique identifier, an
   additional element be specified.  The default value for this
      object is defined belonging to both the two groups. IANA assigned port, 33434, for the traceroute
      measurement.
   o  dataType - Unsigned32
   o  units - UDP Port





Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 10] 8]

Internet-Draft          Traceroute Storage Format          February            August 2007


5.2.1.  Configuration Information Elements

   This section describes the elements of the traceroute measurement
   that are specific to traceroute configuration.

5.2.1.1.  CtlTargetAddressType


   o  default value - 33434

5.2.1.8.  CtlMaxTtl

   o  name - CtlTargetAddressType CtlMaxTtl
   o  description - Specifies the type of host address used in maximum TTL value for the traceroute command.
      measurement.
   o  dataType - InetAddressType Unsigned32
   o  units - N/A time-to-live value
   o  default value - N/A

5.2.1.2.  CtlTargetAddress 30

5.2.1.9.  CtlDSField

   o  name - CtlTargetAddress CtlDSField
   o  description - Specifies the host address used value that was stored in the
      Differentiated Services (DS) field in the traceroute
      command. probe.  The host address type can be determined by the examining
      DS Field is defined as the value Type of Service (TOS) octet in a IPv4
      header or as the corresponding CtlTargetAddressType. Traffic Class octet in a IPv6 header.  The value
      of this object must be a decimal integer in the range from 0 to
      255.  This option can be used to determine what effect an explicit
      DS field setting has on a traceroute measurement and its probes.
      Not all values are legal or meaningful.  Useful TOS octet values
      are probably '16' (low delay) and '8' (high throughput).  Further
      references can be found in [RFC2474] for the definition of the
      Differentiated Services (DS) field and to [RFC1812] Section 5.3.2
      for Type of Service (TOS).
   o  dataType - InetAddress Unsigned32
   o  units - N/A
   o  default value - N/A

5.2.1.3.  CtlByPassRouteTable 0

5.2.1.10.  CtlSourceAddressType

   o  name - CtlByPassRouteTable CtlSourceAddressType
   o  description - Specifies if the optional bypassing type of the route
      table was enabled or not.  If enabled, the traceroute will bypass
      the normal routing tables and send directly to a host on an
      attached network.  If the host is not on a directly-attached
      network, an error is returned.  This option can be source address,
      CtlSourceAddress, used to perform in the traceroute operation to a local host through an interface that
      has no route defined. measurement.
   o  dataType - TruthValue InetAddressType
   o  units - N/A
   o  default value - false

5.2.1.4.  CtlProbeDataSize N/A

5.2.1.11.  CtlSourceAddress

   o  name - CtlProbeDataSize CtlSourceAddress
   o  description - Specifies the size of the data portion of IP address (which has to be given as
      an IP number, not a
      traceroute operation in octets.  If the RECOMMENDED traceroute
      method (UDP datagrams hostname) as probes) is used, then the value contained source address used in this object is exact.  If another
      traceroute method is used for
      which the specified size is not appropriate, then the
      implementation should have probes.  On hosts with more than one IP address, this
      option can be used whatever size (appropriate to force the
      method) is closest source address to be something
      other than the specified size.  The maximum primary IP address of the interface the probe is
      sent on.  A zero length octet string value for this object means



Niccolini, et al.       Expires August 26, 2007 February 25, 2008               [Page 11] 9]

Internet-Draft          Traceroute Storage Format          February            August 2007


      that source address specification was disabled.  The address type
      (InetAddressType) that relates to this object was computed is specified by substracting the smallest possible IP
      header size of 20 octets (IPv4 header with no options) and the UDP
      header size of 8 octets from the maximum IP packet size.  An IP
      packet has a maximum size
      corresponding value of 65535 octets (excluding IPv6
      Jumbograms). CtlSourceAddressType.
   o  dataType - Unsigned32 InetAddress
   o  units - octects N/A
   o  default value - 0

5.2.1.5.  CtlTimeOut N/A

5.2.1.12.  CtlIfIndex

   o  name - CtlTimeOut CtlIfIndex
   o  description - Specifies the time-out value, interface index used in seconds, the traceroute
      measurement for sending the traceroute operation. probes.  A value of zero
      for this object implies that the interface was unknown.
   o  dataType - Unsigned32 InterfaceIndexOrZero
   o  units - seconds N/A
   o  default value - 3

5.2.1.6.  CtlProbesPerHop 0

5.2.1.13.  CtlMiscOptions

   o  name - CtlProbesPerHop CtlMiscOptions
   o  description - Specifies implementation dependent options.
   o  dataType - String
   o  units - N/A
   o  default value - N/A

5.2.1.14.  CtlMaxFailures

   o  name - CtlMaxFailures
   o  description - Specifies the maximum number of times to reissue consecutive timeouts
      allowed before terminating a traceroute request with measurement.  A value of
      either 255 (maximum hop count/possible TTL value) or a 0 indicates
      that the same time-to-live (TTL) value. function of terminating a remote traceroute measurement
      when a specific number of consecutive timeouts are detected was
      disabled.  This element is included to give full compatibility
      with [RFC4560].  No known implementation of traceroute currently
      supports it.
   o  dataType - Unsigned32
   o  units - probes timeouts
   o  default value - 3

5.2.1.7.  CtlPort 5

5.2.1.15.  CtlDontFragment

   o  name - CtlPort CtlDontFragment
   o  description - Specifies if the base UDP port used by the traceroute
      operation.  Need to specify a port that is not don't fragment flag (DF) in use at the
      destination (target) host.  The default value IP
      header for this object is a probe was enabled or not.  Setting the IANA assigned port, 33434, DF flag can be
      used for the traceroute function. performing a manual PATH MTU test.





Niccolini, et al.       Expires February 25, 2008              [Page 10]

Internet-Draft          Traceroute Storage Format            August 2007


   o  dataType - Unsigned32 TruthValue
   o  units - UDP Port N/A
   o  default value - 33434

5.2.1.8.  CtlMaxTtl false

5.2.1.16.  CtlInitialTtl

   o  name - CtlMaxTtl CtlInitialTtl
   o  description - Specifies the maximum initial TTL value for the used in a traceroute
      operation.
      measurement.  Such TTL setting is intended to bypass the initial
      (often well known) portion of a path.
   o  dataType - Unsigned32
   o  units - time-to-live value N/A
   o  default value - 30





Niccolini, et al.        Expires August 26, 2007               [Page 12]

Internet-Draft          Traceroute Storage Format          February 2007


5.2.1.9.  CtlDSField 1

5.2.1.17.  CtlDescr

   o  name - CtlDSField CtlDescr
   o  description - Specifies the value that was stored in the
      Differentiated Services (DS) field in the IP packet used to
      encapsulate the traceroute probe.  The DS Field is defined as the
      Type of Service (TOS) octet in a IPv4 header or as the Traffic
      Class octet in a IPv6 header. The value purpose of this object must be a
      decimal integer in the range from 0 to 255.  This option can be
      used element is to determine what effect an explicit DS field setting has on provide a traceroute response.  Not all values are legal or meaningful.
      Useful TOS octet values are probably '16' (low delay) and '8'
      (high throughput).  Further references can be found in [RFC2474]
      for the definition
      description of the Differentiated Services (DS) field and
      to [RFC1812] Section 5.3.2 for Type of Service (TOS). traceroute measurement.
   o  dataType - Unsigned32 String
   o  units - N/A
   o  default value - 0

5.2.1.10.  CtlSourceAddressType N/A

5.2.1.18.  CtlType

   o  name - CtlSourceAddressType CtlType
   o  description - Specifies the type of the source address,
      CtlSourceAddress, implementation method used when performing for the
      traceroute operation. measurement.  It specifies if the traceroute is using
      TCP, UDP or ICMP probes.
   o  dataType - InetAddressType ProbesType
   o  units - N/A
   o  default value - N/A

5.2.1.11.  CtlSourceAddress UDP

5.2.2.  Results Information Elements

   This section describes the elements specific to the results of the
   traceroute measurement.

5.2.2.1.  ResultsStartDateAndTime

   o  name - CtlSourceAddress ResultsStartDateAndTime
   o  description - Specifies the IP address (which has to be given as
      an IP number, not a hostname) as the source address used in
      outgoing probe packets.  On hosts with more than one IP address,
      this option can be used to force the source address to be
      something other than the primary IP address date and start time of the interface traceroute
      measurement.  This is the time when the first probe packet is sent on.  A zero length octet string value for
      this object means that source address specification was disabled.
      The address type (InetAddressType) that relates to this object is
      specified by seen at
      the corresponding value of CtlSourceAddressType. sending interface.
   o  dataType - InetAddress DateAndTime
   o  units - N/A
   o  default value - N/A

5.2.1.12.  CtlIfIndex





Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 13] 11]

Internet-Draft          Traceroute Storage Format          February            August 2007


   o  name - CtlIfIndex
   o  description - Specifies the inferface index used in the traceroute
      operation for sending the traceroute probes.  A value of zero for
      this object implies that the interface was unknown.
   o  dataType - InterfaceIndexOrZero
   o  units - N/A
   o  default value - 0

5.2.1.13.  CtlMiscOptions N/A

5.2.2.2.  ResultsIpTgtAddrType

   o  name - CtlMiscOptions ResultsIpTgtAddrType
   o  description - Specifies implementation dependent options. the type of address stored in the
      corresponding ResultsIpTgtAddr element.
   o  dataType - String InetAddressType
   o  units - N/A
   o  default value - N/A

5.2.1.14.  CtlMaxFailures

5.2.2.3.  ResultsIpTgtAddr

   o  name - CtlMaxFailures ResultsIpTgtAddr
   o  description - Specifies the maximum number of consecutive timeouts
      allowed before terminating IP address associated with a traceroute operation.  A
      CtlTargetAddress value of
      either 255 (maximum hop count/possible TTL value) or a 0 indicates
      that when the function destination address is specified
      as a DNS name.  The value of terminating this object should be a remote traceroute operation zero length
      octet string when a specific number of consecutive timeouts are detected was
      disabled.  This element DNS name is included not specified or when a specified
      DNS name fails to give full compatibility
      with [RFC4560].  No known implementation of traceroute currently
      supports it. resolve.
   o  dataType - Unsigned32 InetAddress
   o  units - timeouts N/A
   o  default value - 5

5.2.1.15.  CtlDontFragment N/A

5.2.2.4.  Index

   o  name - CtlDontFragment Index
   o  description - Specifies if the don't fragment flag (DF) in the IP
      header an index that consecutively numbers all
      probes for which a probe reply was enabled or not.  Setting received in the DF flag can be
      used sequential order in
      which the replies were received.  The maximum value for performing a manual PATH MTU test. this
      object is CtlMaxTtl*CtlProbesPerHop.
   o  dataType - TruthValue Unsigned32
   o  units - N/A
   o  default value - false

5.2.1.16.  CtlInitialTtl N/A

5.2.2.5.  HopIndex

   o  name - CtlInitialTtl HopIndex
   o  description - Specifies the initial TTL value used which hop in a traceroute
      operation.  Such TTL setting is intended to bypass measurement path
      the initial
      (often well known) portion of a path.




Niccolini, et al.        Expires August 26, 2007               [Page 14]

Internet-Draft          Traceroute Storage Format          February 2007 probe's results are for.
   o  dataType - Unsigned32
   o  units - N/A
   o  default value - 1

5.2.1.17.  CtlDescr N/A

5.2.2.6.  IndexPerHop

   o  name - CtlDescr IndexPerHop





Niccolini, et al.       Expires February 25, 2008              [Page 12]

Internet-Draft          Traceroute Storage Format            August 2007


   o  description - Specifies the index of a probe for a particular hop
      in a traceroute measurement path.  The purpose number of this element probes per hop is to provide a
      description
      determined by the value of the traceroute test. corresponding CtlProbesPerHop
      element.
   o  dataType - String Unsigned32
   o  units - N/A
   o  default value - N/A

5.2.1.18.  CtlType

   o  name - CtlType
   o  description - Specifies the implementation method used for the
      traceroute operation.  It specifies if the traceroute is using
      TCP, UDP or ICMP probes.
   o  dataType - ProbesType
   o  units - N/A
   o  default value - UDP

5.2.2.  Results Information Elements

   This section describes the elements of the traceroute measurement
   that are specific to the results of a traceroute operation.

5.2.2.1.  ResultsStartDateAndTime

   o  name - ResultsStartDateAndTime
   o  description - Specifies the date and start time of the traceroute
      operation.  This is the time when the first probe was seen at the
      sending interface.
   o  dataType - DateAndTime
   o  units - N/A
   o  default value - N/A

5.2.2.2.  ResultsIpTgtAddrType

5.2.2.7.  HopAddrType

   o  name - ResultsIpTgtAddrType HopAddrType
   o  description - Specifies the type of address stored in the
      corresponding ResultsIpTgtAddr HopAddr element.
   o  dataType - InetAddressType
   o  units - N/A
   o  default value - N/A





Niccolini, et al.        Expires August 26, 2007               [Page 15]

Internet-Draft          Traceroute Storage Format          February 2007


5.2.2.3.  ResultsIpTgtAddr

5.2.2.8.  HopAddr

   o  name - ResultsIpTgtAddr HopAddr
   o  description - Specifies the IP address associated with of a
      CtlTargetAddress value when hop in the destination address traceroute
      measurement path.  This object is specified
      as not allowed to be a DNS name.
      The value of the corresponding object, HopAddrType, indicates this object should be a zero length
      octet string when a DNS name is not specified or when a specified
      DNS name fails to resolve.
      object's IP address type.
   o  dataType - InetAddress
   o  units - N/A
   o  default value - N/A

5.2.2.4.  Index

5.2.2.9.  HopGeoLocation

   o  name - Index HopGeoLocation
   o  description - Specifies an index that consecutively numbers all
      probes for which a reply was received in the sequential order geo location of a hop in
      which the replies were received.  The maximum value for this
      object is CtlMaxTtl*CtlProbesPerHop.
      traceroute measurement path.
   o  dataType - Unsigned32 String
   o  units - N/A
   o  default value - N/A

5.2.2.5.  HopIndex

5.2.2.10.  MPLSTopLabel

   o  name - HopIndex
   o  description - Specifies which hop in a traceroute path that the
      probe's results are for.
   o  dataType - Unsigned32
   o  units - N/A
   o  default value - N/A

5.2.2.6.  IndexPerHop

   o  name - IndexPerHop
   o  description - Specifies the index of a probe for a particular hop
      in a traceroute path.  The number of probes per hop is determined
      by the value of the corresponding CtlProbesPerHop element.
   o  dataType - Unsigned32
   o  units - N/A
   o  default value - N/A

5.2.2.7.  HopAddrType

   o  name - HopAddrType
   o  description - Specifies the type of address stored in the
      corresponding HopAddr element.




Niccolini, et al.        Expires August 26, 2007               [Page 16]

Internet-Draft          Traceroute Storage Format          February 2007


   o  dataType - InetAddressType
   o  units - N/A
   o  default value - N/A

5.2.2.8.  HopAddr

   o  name - HopAddr
   o  description - Specifies the address of a hop in the traceroute
      path.  This object is not allowed to be a DNS name.  The value of
      the corresponding object, HopAddrType, indicates this object's IP
      address type.
   o  dataType - InetAddress
   o  units - N/A
   o  default value - N/A

5.2.2.9.  HopGeoLocation

   o  name - HopGeoLocation
   o  description - Specifies the geo location of a hop in the
      traceroute path.
   o  dataType - String
   o  units - N/A
   o  default value - N/A

5.2.2.10.  MPLSTopLabel

   o  name - MPLSTopLabel MPLSTopLabel
   o  description - Specifies the top entry of the MPLS label stack of a
      probe observed when the probe arrived at the hop that replied to
      the probe.  This object contains the top MPLS label stack entry as
      32 bit value as it is observed on the MPLS label stack.  Contained
      in this single number are the MPLS label, the Exp field, the S
      flag, and the MPLS TTL value as specified in RFC 3032 [RFC3032]. 3032.





Niccolini, et al.       Expires February 25, 2008              [Page 13]

Internet-Draft          Traceroute Storage Format            August 2007


   o  dataType - Unsigned32
   o  units - N/A
   o  default value - N/A

5.2.2.11.  RoundTripTime

   o  name - RoundTripTime
   o  description - Specifies the amount of time measured in
      milliseconds from when a probe was sent to when its response was
      received or when it timed out.  The value of this element is
      reported as the truncation of the number reported by the
      traceroute tool (the output "< 1 ms" is therefore encoded as 0
      ms).  A string with the value of "RoundTripTimeNotAvailable" means
      either the probe was lost because of a timeout or it was not
      possible to transmit a probe.



Niccolini, et al.        Expires August 26, 2007               [Page 17]

Internet-Draft          Traceroute Storage Format          February 2007
   o  dataType - Unsigned32 or String
   o  units - milliseconds or N/A
   o  default value - N/A

5.2.2.12.  ResponseStatus

   o  name - ResponseStatus
   o  description - Specifies the result of a traceroute operation measurement
      made by the host for a particular probe.
   o  dataType - OperationResponseStatus
   o  units - N/A
   o  default value - N/A

5.2.2.13.  Time

   o  name - Time
   o  description - Specifies the timestamp for when the response to the
      probe was received at the interface.
   o  dataType - DateAndTime
   o  units - N/A
   o  default value - N/A

5.2.2.14.  ResultsHopRawOutputData

   o  name - ResultsHopRawOutputData
   o  description - Specifies the raw output data returned by the
      traceroute operation measurement for a certain hop in a traceroute
      measurement path.
   o  dataType - String
   o  units - N/A
   o  default value - N/A





Niccolini, et al.       Expires February 25, 2008              [Page 14]

Internet-Draft          Traceroute Storage Format            August 2007


5.2.2.15.  ResultsEndDateAndTime

   o  name - ResultsEndDateAndTime
   o  description - Specifies the date and end time of the traceroute
      operation.
      measurement.  It is either the time when the response to the last
      probe of the traceroute operation measurement was received or the time when
      the last probe of the traceroute operation measurement was sent plus the
      relative timeout (in case of missing response).
   o  dataType - DateAndTime
   o  units - N/A
   o  default value - N/A

5.2.3.  Information Element Correlating Configuration and Results
        Elements

   This section defines an additional element belonging to both the two
   previous groups. groups (configuration elements and result elements) named
   TestName.  This element is defined in order to relate



Niccolini, et al.        Expires August 26, 2007               [Page 18]

Internet-Draft          Traceroute Storage Format          February 2007 configuration
   elements and results ones by means of a common unique identifier.

5.2.3.1.  TestName

   o  name - TestName
   o  description - Specifies the name of a traceroute test. measurement.
      This is locally unique.
   o  dataType - String
   o  units - N/A
   o  default value - N/A

5.2.4.  Information Elements to compare traceroute measurements results
        one with each other

   This section defines additional elements belonging to both the two
   previous groups (configuration elements and result elements); these
   elements were defined in order to allow traceroute measurements
   results comparison among different traceroute measurements.

5.2.4.1.  OSName

   o  name - OSName
   o  description - Specifies the name of the operating system on which
      the traceroute measurement was launched.
   o  dataType - String
   o  units - N/A
   o  default value - N/A






Niccolini, et al.       Expires February 25, 2008              [Page 15]

Internet-Draft          Traceroute Storage Format            August 2007


5.2.4.2.  OSVersion

   o  name - OSVersion
   o  description - Specifies the OS version on which the traceroute
      measurement was launched.
   o  dataType - String
   o  units - N/A
   o  default value - N/A

5.2.4.3.  ToolVersion

   o  name - ToolVersion
   o  description - Specifies the version of the traceroute tool used.
   o  dataType - String
   o  units - N/A
   o  default value - N/A


6.  Data Model for Storing Traceroute Measurements

   For storing and transmitting information according to the information
   model defined in the previous section, a data model is required that
   specifies how to encode the elements of the information model.

   There are several design choices for a data model.  It can use a
   binary or textual representation and it can be defined from scratch
   or use already existing frameworks and data models.  In general, the
   use of already existing frameworks and models should be preferred.

   Binary and textual representation both have advantages and
   disadvantages.  Textual representions representations are (with some limitations)
   human readable while a binary representation consumes less resources
   for storing, transmitting and parsing data.

   An already existing and closely related data model is the DISMAN-
   TRACEROUTE-MIB module [RFC4560], that specifies a BER encoding
   [RFC3417] used by the Simple Network Management Protocol (SNMP)
   [RFC3410] for transmitting traceroute information. measurement information
   (configuration and results).  This data model is well suited and
   supported within network management systems, but as a general format
   for storing and transmitting traceroute results it is not easily
   applicable.

   Another binary representation would be an extension of traffic flow
   information encodings as specified for the IPFIX protocol
   [I-D.ietf-ipfix-protocol], [I-D.ietf-ipfix-info].  The IPFIX protocol
   is extensible.  However, the architecture behind this protocol
   [I-D.ietf-ipfix-architecture] is targeted at exporting passively



Niccolini, et al.       Expires February 25, 2008              [Page 16]

Internet-Draft          Traceroute Storage Format            August 2007


   measured flow information.  Therefore, some obstacles are expected
   when trying to use it for transmitting traceroute measurement
   results. measurements
   information.

   For textual representations, using the eXtensible Markup Language
   (XML) [XML] is an obvious choice.  XML supports clean structuring of



Niccolini, et al.        Expires August 26, 2007               [Page 19]

Internet-Draft          Traceroute Storage Format          February 2007
   data and syntax checking of records.  With some limitations it is
   human readable.  It is supported well by a huge pool of tools and
   standards for generating, transmitting, parsing and converting it to
   other data formats.  Its disadvantages is the resource comsumption consumption
   for processing, storing, and transmitting information.  Since the
   expected data volumes of related to traceroute data measurements in network
   operation and maintenance is not expected to be extremly extremely high, the
   inefficient usage of resources is not a significant disadvantage.
   Therefore, XML was chosen as basis for the traceroute measurements
   information model that is specified in this section.

   Section 7 contains the XML schema to be used as a template for
   storing and/or exchanging traceroute measurements. measurements information.  The
   schema was designed in order to use an extensible approach based on
   templates (pretty similar to how IPFIX protocol is designed) where
   the traceroute configuration elements (both the requested parameters,
   Request, and the actual parameters used, MeasurementMetadata) are
   metadata to be referenced by results information elements (data) by
   means of the TestName element (used as unique identifier).  Currently
   Global
   Open Grid Forum (GGF) (OGF) is also using this approach and cross-
   requirements have been analyzed.  As a result of this analysis the
   XML schema contained in Section 7 is compatible with GGF OGF schema since
   it was designed in a way that both limits the unecessary unnecessary redundancy
   and a simple one-to-one trasformation transformation between the two exist.


7.  XML Schema for traceroute Measurements

   <?xml version="1.0" encoding="UTF-8"?>
   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
              targetNamespace="urn:ietf:params:xml:ns:traceroute-1.0">

     <xs:simpleType name="inetAddressType">
       <xs:restriction base="xs:string">
         <xs:enumeration value="unknown"/>
         <xs:enumeration value="ipv4"/>
         <xs:enumeration value="ipv6"/>
         <xs:enumeration value="dns"/>
         <xs:enumeration value="asnumber"/>
       </xs:restriction>
     </xs:simpleType>




Niccolini, et al.       Expires February 25, 2008              [Page 17]

Internet-Draft          Traceroute Storage Format            August 2007


     <xs:simpleType name="inetAddressTypeWithoutDns">
       <xs:restriction base="xs:string">
         <xs:enumeration value="unknown"/>
         <xs:enumeration value="ipv4"/>
         <xs:enumeration value="ipv6"/>
         <xs:enumeration value="asnumber"/>



Niccolini, et al.        Expires August 26, 2007               [Page 20]

Internet-Draft          Traceroute Storage Format          February 2007
         <xs:enumeration value="noSpecification"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_zeroLengthString">
       <xs:restriction base="xs:string">
         <xs:maxLength value="0"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_inetAddressIpv4">
       <xs:restriction base="xs:string">
         <xs:pattern value="(([1-9]?[0-9]|1[0-9][0-9]|
         2[0-4][0-9]|25[0-5]).){3}([1-9]?[0-9]|1[0-9]
         [0-9]|2[0-4][0-9]|25[0-5])"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_inetAddressIpv6">
       <xs:restriction base="xs:string">
         <xs:pattern value="(([\dA-Fa-f]{1,4}:){7}[\dA-Fa-f]{1,4})
         (:([\d]{1,3}.){3}[\d]{1,3})?"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_inetAddressDns">
       <xs:restriction base="xs:string">
         <xs:maxLength value="256"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_asNumber">
       <xs:restriction base="xs:unsignedInt"/>
     </xs:simpleType>

     <xs:simpleType name="_ipASNumberMappingType">
       <xs:restriction base="xs:string">
         <xs:enumeration value="bgptables"/>
         <xs:enumeration value="routingregistries"/>
         <xs:enumeration value="nslookup"/>
         <xs:enumeration value="others"/>
         <xs:enumeration value="unknown"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="operationResponseStatus">
       <xs:restriction base="xs:string">
         <xs:enumeration value="responseReceived"/>



Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 21] 18]

Internet-Draft          Traceroute Storage Format          February            August 2007


       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="operationResponseStatus">
       <xs:restriction base="xs:string">
         <xs:enumeration value="responseReceived"/>
         <xs:enumeration value="unknown"/>
         <xs:enumeration value="internalError"/>
         <xs:enumeration value="requestTimedOut"/>
         <xs:enumeration value="unknownDestinationAddress"/>
         <xs:enumeration value="noRouteToTarget"/>
         <xs:enumeration value="interfaceInactiveToTarget"/>
         <xs:enumeration value="arpFailure"/>
         <xs:enumeration value="maxConcurrentLimitReached"/>
         <xs:enumeration value="unableToResolveDnsName"/>
         <xs:enumeration value="invalidHostAddress"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_dateAndTimeUpToSeconds">
       <xs:restriction base="xs:dateTime"/>
     </xs:simpleType>

     <xs:simpleType name="_timeMilliseconds">
       <xs:restriction base="xs:unsignedShort">
         <xs:maxExclusive value="1000"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_TestName">
       <xs:annotation>
         <xs:documentation>Specifies the name of a
         traceroute
         test. measurement. This is locally unique.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="32"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_OSName">
       <xs:annotation>
         <xs:documentation>Specifies the name of the operating
         system on which the traceroute measurement was
         launched.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">



Niccolini, et al.       Expires February 25, 2008              [Page 19]

Internet-Draft          Traceroute Storage Format            August 2007


         <xs:maxLength value="32"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_OSVersion">
       <xs:annotation>
         <xs:documentation>Specifies the OS version on which the



Niccolini, et al.        Expires August 26, 2007               [Page 22]

Internet-Draft          Traceroute Storage Format          February 2007
         traceroute measurement was launched.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="32"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_ToolVersion">
       <xs:annotation>
         <xs:documentation>Specifies the version of the traceroute
         tool used.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="32"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlByPassRouteTable"> name="_CtlBypassRouteTable">
       <xs:annotation>
         <xs:documentation>Specifies if the optional bypassing
         of the route table was enabled or not. If enabled,
         the traceroute will bypass the normal routing tables will be bypassed and send the
         probes will be sent directly to a host on an attached
         network. If the host is not on a directly-attached
         network, an error is returned.  This option can be
         used to perform the traceroute operation measurement to a
         local host through an interface that has no route
         defined.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:boolean"/>
     </xs:simpleType>

     <xs:simpleType name="_CtlProbeDataSize">
       <xs:annotation>
         <xs:documentation>Specifies the size of the data
         portion probes
         of a traceroute operation measurement in octets. If the
         RECOMMENDED traceroute method (UDP UDP
         datagrams are used as probes)
         is used, probes, then the value
         contained in this object is exact. If another traceroute method



Niccolini, et al.       Expires February 25, 2008              [Page 20]

Internet-Draft          Traceroute Storage Format            August 2007


         protocol is used to transmit probes (i.e. TCP or
         ICMP) for which the specified size is not
         appropriate, then the implementation should have used can use
         whatever size (appropriate to the method) is
         closest to the specified size. The maximum value
         for this object was computed by
         substracting subtracting the
         smallest possible IP header size of 20 octets (IPv4
         header with no options) and the UDP header size of
         8 octets from the maximum IP packet size. An IP



Niccolini, et al.        Expires August 26, 2007               [Page 23]

Internet-Draft          Traceroute Storage Format          February 2007
         packet has a maximum size of 65535 octets (excluding
         IPv6
         jumbograms). Units are: octects. Jumbograms).
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedShort">
         <xs:maxExclusive value="65508"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlTimeOut">
       <xs:annotation>
         <xs:documentation>Specifies the time-out value, in
         seconds, for the each probe of a traceroute operation.
         Units are: seconds. measurement.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte">
         <xs:minExclusive value="0"/>
         <xs:maxExclusive value="61"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlProbesPerHop">
       <xs:annotation>
         <xs:documentation>Specifies the number of times to
         reissue a traceroute request probes
         with the same time-to-live (TTL) value. Units are: probes. value that are
         sent for each host.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte">
         <xs:minExclusive value="0"/>
         <xs:maxExclusive value="11"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlPort">
       <xs:annotation>
         <xs:documentation>Specifies the base UDP port used
         by the traceroute operation.  Need to specify a measurement. A port that is not
         in use at the destination (target) host. host needs to be



Niccolini, et al.       Expires February 25, 2008              [Page 21]

Internet-Draft          Traceroute Storage Format            August 2007


         specified. The default value for this object is the
         IANA assigned port, 33434, for the traceroute function.
         Units are: UDP port.
         measurement.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedShort">
         <xs:minExclusive value="0"/>
       </xs:restriction>



Niccolini, et al.        Expires August 26, 2007               [Page 24]

Internet-Draft          Traceroute Storage Format          February 2007
     </xs:simpleType>

     <xs:simpleType name="_CtlMaxTtl">
       <xs:annotation>
         <xs:documentation>Specifies the maximum TTL value
         for the traceroute operation.
         Units are: time-to-live value. measurement.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte">
         <xs:minExclusive value="0"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlDSField">
       <xs:annotation>
         <xs:documentation>Specifies the value that was
         stored in the Differentiated Services (DS) field
         in the IP packet
         used to encapsulate the traceroute probe. The DS Field is defined
         as the Type of Service (TOS) octet in a IPv4 header
         or as the Traffic Class octet in a IPv6 header.
         The value of this object must be a decimal integer
         in the range from 0 to 255. This option can be
         used to determine what effect an explicit DS field
         setting has on a traceroute response. measurement and its
         probes. Not all values are legal or meaningful.
         Useful TOS octet values are probably '16' (low
         delay) and '8' (high throughput). Further references
         can be found in the RFC 2474 for the definition of the
         Differentiated Services (DS) field and to the RFC 1812
         Section 5.3.2 for Type of Service (TOS).
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte"/>
     </xs:simpleType>

     <xs:simpleType name="_CtlIfIndex">
       <xs:annotation>
         <xs:documentation>Specifies the inferface interface index
         used in the traceroute operation measurement for sending
         the traceroute probes. A value of zero for this



Niccolini, et al.       Expires February 25, 2008              [Page 22]

Internet-Draft          Traceroute Storage Format            August 2007


         object implies that the interface was unknown.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte"/>
     </xs:simpleType>

     <xs:simpleType name="_CtlMiscOptions">



Niccolini, et al.        Expires August 26, 2007               [Page 25]

Internet-Draft          Traceroute Storage Format          February 2007
       <xs:annotation>
         <xs:documentation>Specifies implementation dependent
         options.</xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="100"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlMaxFailures">
       <xs:annotation>
         <xs:documentation>Specifies the maximum number
         of consecutive timeouts allowed before terminating
         a traceroute operation. measurement. A value of either 255
         (maximum hop count/possible TTL value) or a 0
         indicates that the function of terminating a
         remote traceroute
         operation measurement when a specific
         number of consecutive timeouts are detected was
         disabled. This element is included to give full
         compatibility with DISMAN working
         group documents. RFC 4560. No known implementation
         of traceroute currently supports it.
         Units are: timeouts.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte"/>
     </xs:simpleType>

     <xs:simpleType name="_CtlDontFragment">
       <xs:annotation>
         <xs:documentation>Specifies if the don't fragment
         flag (DF) in the IP header for a probe was enabled
         or not. Setting the DF flag can be used for
         performing a manual PATH MTU test.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:boolean"/>
     </xs:simpleType>

     <xs:simpleType name="_CtlInitialTtl">
       <xs:annotation>
         <xs:documentation>Specifies the initial TTL
         value used in a traceroute operation. measurement. Such



Niccolini, et al.       Expires February 25, 2008              [Page 23]

Internet-Draft          Traceroute Storage Format            August 2007


         TTL setting is intended to bypass the initial
         (often well known) portion of a path.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte">
         <xs:minExclusive value="0"/>



Niccolini, et al.        Expires August 26, 2007               [Page 26]

Internet-Draft          Traceroute Storage Format          February 2007
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlDescr">
       <xs:annotation>
         <xs:documentation>The purpose of this element
         is to provide a description of the traceroute test.
         measurement.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="100"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_CtlType">
       <xs:annotation>
         <xs:documentation>Specifies the implementation
         method used for the traceroute operation. measurement.
         It specifies if the traceroute is using TCP,
         UDP or ICMP probes.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:enumeration value="TCP"/>
         <xs:enumeration value="UDP"/>
         <xs:enumeration value="ICMP"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_Index">
       <xs:annotation>
         <xs:documentation>Specifies an index that
         consecutively numbers all probes for which
         a reply was received in the sequential order
         in which the replies were received. The
         maximum value for this object is
         CtlMaxTtl*CtlProbesPerHop.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedShort">
         <xs:minExclusive value="0"/>



Niccolini, et al.       Expires February 25, 2008              [Page 24]

Internet-Draft          Traceroute Storage Format            August 2007


         <xs:maxExclusive value="2551"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_HopIndex">
       <xs:annotation>
         <xs:documentation>Specifies which hop in a
         traceroute measurement path that the probe's
         results are for. The value of
         this element is initially determined by the value of



Niccolini, et al.        Expires August 26, 2007               [Page 27]

Internet-Draft          Traceroute Storage Format          February 2007


         CtlInitialTtl.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte">
         <xs:minExclusive value="0"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_IndexPerHop">
       <xs:annotation>
         <xs:documentation>Specifies the index of a
         probe for a particular hop in a traceroute
         measurement path. The number of probes per hop
         is determined by the value of the corresponding
         CtlProbesPerHop element.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedByte">
         <xs:minExclusive value="0"/>
         <xs:maxExclusive value="11"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_HopGeoLocation">
       <xs:annotation>
         <xs:documentation>Specifies the geo location of a
         hop in the traceroute measurement path.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="100"/>
       </xs:restriction>
     </xs:simpleType>

    <xs:simpleType name="_MPLSTopLabel">
       <xs:annotation>
         <xs:documentation>Specifies the top entry of the
         MPLS label stack of a probe observed when the probe
         arrived at the hop that replied to the probe.
         This object contains the top MPLS label stack



Niccolini, et al.       Expires February 25, 2008              [Page 25]

Internet-Draft          Traceroute Storage Format            August 2007


         entry as 32 bit value as it is observed on the MPLS
         label stack. Contained in this single number are the
         MPLS label, the Exp field, the S flag, and the MPLS
         TTL value as specified in RFC 3032 [RFC3032]. 3032.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:unsignedInt">
         <xs:maxExclusive value="4294967296"/>
         <xs:maxInclusive value="4294967295"/>
       </xs:restriction>
     </xs:simpleType>



Niccolini, et al.        Expires August 26, 2007               [Page 28]

Internet-Draft          Traceroute Storage Format          February 2007

     <xs:simpleType name="_probeRoundTripTime">
       <xs:restriction base="xs:unsignedShort">
         <xs:maxExclusive value="60001"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_probeRoundTripTimeNotAvailable">
       <xs:restriction base="xs:string">
         <xs:enumeration value="NotAvailable"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="_ResultsHopRawOutputData">
       <xs:annotation>
         <xs:documentation>Specifies the raw output data
         returned by the traceroute operation measurement for a certain
         hop in a traceroute measurement path.
         </xs:documentation>
       </xs:annotation>
       <xs:restriction base="xs:string">
         <xs:maxLength value="200"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:complexType name="_inetAddressASNumber">
       <xs:annotation>
         <xs:documentation>Specifies the AS number of a hop in the
         traceroute path as a 24 bit number and the indication how
         the mapping from IP address to AS number was performed.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="asNumber"
                     type="_asNumber"/>
         <xs:element name="ipASNumberMappingType"
                     type="_ipASNumberMappingType"/>
       </xs:sequence>



Niccolini, et al.       Expires February 25, 2008              [Page 26]

Internet-Draft          Traceroute Storage Format            August 2007


     </xs:complexType>

     <xs:complexType name="_inetAddress">
       <xs:choice>
         <xs:element name="inetAddressUnknown"
                     type="_zeroLengthString"/>
         <xs:element name="inetAddressIpv4"
                     type="_inetAddressIpv4"/>
         <xs:element name="inetAddressIpv6"
                     type="_inetAddressIpv6"/>
         <xs:element name="inetAddressDns"
                     type="_inetAddressDns"/>



Niccolini, et al.        Expires August 26, 2007               [Page 29]

Internet-Draft          Traceroute Storage Format          February 2007
         <xs:element name="inetAddressASNumber"
                     type="_inetAddressASNumber"/>
       </xs:choice>
     </xs:complexType>

     <xs:complexType name="_inetAddressWithoutDns">
       <xs:choice>
         <xs:element name="inetAddressUnknown"
                     type="_zeroLengthString"/>
         <xs:element name="inetAddressIpv4"
                     type="_inetAddressIpv4"/>
         <xs:element name="inetAddressIpv6"
                     type="_inetAddressIpv6"/>
         <xs:element name="inetAddressASNumber"
                     type="_inetAddressASNumber"/>
         <xs:element name="zeroLengthString"
                     type="_zeroLengthString"/>
       </xs:choice>
     </xs:complexType>

     <xs:complexType name="_dateAndTime">
       <xs:sequence>
         <xs:element name="dateAndTimeUpToSeconds"
                     type="_dateAndTimeUpToSeconds"/>
         <xs:element name="timeMilliseconds"
                     type="_timeMilliseconds"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_CtlTargetAddressType">
       <xs:annotation>
         <xs:documentation>Specifies the type of host destination
         address used in the traceroute command. measurement.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>



Niccolini, et al.       Expires February 25, 2008              [Page 27]

Internet-Draft          Traceroute Storage Format            August 2007


         <xs:element name="targetAddressType"
                     type="inetAddressType"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_CtlTargetAddress">
       <xs:annotation>
         <xs:documentation>Specifies the host address
         used in the traceroute command. measurement. The host
         address type can be determined by the examining
         the value of the corresponding CtlTargetAddressType.
         </xs:documentation>



Niccolini, et al.        Expires August 26, 2007               [Page 30]

Internet-Draft          Traceroute Storage Format          February 2007
       </xs:annotation>
       <xs:sequence>
         <xs:element name="targetAddress" type="_inetAddress"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_CtlSourceAddressType">
       <xs:annotation>
         <xs:documentation>Specifies the type of the source
         address, CtlSourceAddress, used when performing in the traceroute operation.
         measurement.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="sourceAddressType"
                     type="inetAddressTypeWithoutDns"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_CtlSourceAddress">
       <xs:annotation>
         <xs:documentation>Specifies the IP address (which
         has to be given as an IP number, not a hostname)
         as the source address used in outgoing probe packets. traceroute probes.
         On hosts with more than one IP address, this option
         can be used to force the source address to be
         something other than the primary IP address of the
         interface the probe packet is sent on. A zero length
         octet string value for this object means that
         source addres address specification was disabled. The
         address type (InetAddressType) that relates to
         this object is specified by the corresponding
         value of CtlSourceAddressType.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>



Niccolini, et al.       Expires February 25, 2008              [Page 28]

Internet-Draft          Traceroute Storage Format            August 2007


         <xs:element name="sourceAddress"
                     type="_inetAddressWithoutDns"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_ResultsStartDateAndTime">
       <xs:annotation>
         <xs:documentation>Specifies the date and start
         time of the traceroute operation. measurement. This is the
         time when the first probe was sent. seen at the sending
         interface.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>



Niccolini, et al.        Expires August 26, 2007               [Page 31]

Internet-Draft          Traceroute Storage Format          February 2007
         <xs:element name="dateAndTime" type="_dateAndTime"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_ResultsIpTgtAddrType">
       <xs:annotation>
         <xs:documentation>Specifies the type of address stored
         in the corresponding ResultsIpTgtAddr element.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="ipTgtAddrType"
                     type="inetAddressTypeWithoutDns"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_ResultsIpTgtAddr">
       <xs:annotation>
         <xs:documentation>Specifies the IP address associated
         with a CtlTargetAddress value when the destination
         address is specified as a DNS name. The value of
         this object should be a zero length octet string
         when a DNS name is not specified or when a specified
         DNS name fails to resolve.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="ipTgtAddr"
                     type="_inetAddressWithoutDns"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_HopAddrType">
       <xs:annotation>



Niccolini, et al.       Expires February 25, 2008              [Page 29]

Internet-Draft          Traceroute Storage Format            August 2007


         <xs:documentation>Specifies the type of address stored
         in the corresponding HopAddr element.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="probeHopAddrType"
                     type="inetAddressTypeWithoutDns"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_HopAddr">
       <xs:annotation>
         <xs:documentation>Specifies the address of a
         hop in the traceroute measurement path. This
         object is not allowed to



Niccolini, et al.        Expires August 26, 2007               [Page 32]

Internet-Draft          Traceroute Storage Format          February 2007 be a DNS name. The
         value of the corresponding object, HopAddrType,
         indicates this object's IP address type.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="probeHopAddr"
                     type="_inetAddressWithoutDns"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_RoundTripTime">
       <xs:annotation>
         <xs:documentation>Specifies the amount of
         time measured in milliseconds from when a
         probe was sent to when its response was
         received or when it timed out. The value of
         this element is reported as the truncation
         of the number reported by the traceroute
         tool (the output
         "&lt1 "&lt; 1 ms" is therefore
         encoded as 0 ms). A string with the value of
         "RoundTripTimeNotAvailable" means either the
         probe was lost because of a timeout or it
         was not possible to transmit a probe.
         Units are: milliseconds.
         </xs:documentation>
       </xs:annotation>
       <xs:choice>
           <xs:element name="probeRoundTripTime"
                       type="_probeRoundTripTime"/>
           <xs:element name="probeRoundTripTimeNotAvailable"
                       type="_probeRoundTripTime"/>
       </xs:choice>
     </xs:complexType>




Niccolini, et al.       Expires February 25, 2008              [Page 30]

Internet-Draft          Traceroute Storage Format            August 2007


     <xs:complexType name="_ResponseStatus">
       <xs:annotation>
         <xs:documentation>Specifies the result of a traceroute
           operation
         measurement made by the host for a particular probe.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="probeResponseStatus"
                     type="operationResponseStatus"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_Time">
       <xs:annotation>
         <xs:documentation>Specifies the timestamp for
         when the response to the probe was received.



Niccolini, et al.        Expires August 26, 2007               [Page 33]

Internet-Draft          Traceroute Storage Format          February 2007 received at the
         interface.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="dateAndTime" type="_dateAndTime"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_ResultsProbe">
       <xs:sequence>
         <xs:element name="Index"
                     type="_Index"/>
         <xs:element name="HopIndex"
                     type="_HopIndex"/>
         <xs:element name="IndexPerHop"
                     type="_IndexPerHop"/>
         <xs:element name="HopAddrType"
                     type="_HopAddrType"/>
         <xs:element name="HopAddr"
                     type="_HopAddr"/>
         <xs:element name="HopGeoLocation"
                     type="_HopGeoLocation"
                     minOccurs="0" maxOccurs="1"/>
         <xs:element name="MPLSTopLabel"
                     type="_MPLSTopLabel"
                     minOccurs="0" maxOccurs="1"/>
         <xs:element name="RoundTripTime"
                     type="_RoundTripTime"/>
         <xs:element name="ResponseStatus"
                     type="_ResponseStatus"/>
         <xs:element name="Time"
                     type="_Time"/>



Niccolini, et al.       Expires February 25, 2008              [Page 31]

Internet-Draft          Traceroute Storage Format            August 2007


       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_ResultsEndDateAndTime">
       <xs:annotation>
         <xs:documentation>Specifies the date and end time
         of the traceroute operation. measurement. It is either the
         time when the response to the last probe of the
         traceroute
         operation measurement was received or the time
         when the last probe of the traceroute operation measurement
         was sent plus the relative timeout (in case of
         missing response).
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="dateAndTime" type="_dateAndTime"/>
       </xs:sequence>
     </xs:complexType>



Niccolini, et al.        Expires August 26, 2007               [Page 34]

Internet-Draft          Traceroute Storage Format          February 2007

     <xs:complexType name="_Metadata">
       <xs:annotation>
         <xs:documentation>Specifies the metadata for a
         traceroute operation. In a request, these are the
         requested parameters. In a response, they are the
         actual parameters used.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="TestName"
                     type="_TestName"/>
         <xs:element name="OSName"
                     type="_OSName"
                     minOccurs="0" maxOccurs="1"/>
         <xs:element name="OSVersion"
                     type="_OSVersion"
                     minOccurs="0" maxOccurs="1"/>
         <xs:element name="ToolVersion"
                     type="_ToolVersion"
                     minOccurs="0" maxOccurs="1"/>
         <xs:element name="CtlTargetAddressType"
                     type="_CtlTargetAddressType"/>
         <xs:element name="CtlTargetAddress"
                     type="_CtlTargetAddress"/>
         <xs:element name="CtlByPassRouteTable"
                     type="_CtlByPassRouteTable" name="CtlBypassRouteTable"
                     type="_CtlBypassRouteTable"
                     minOccurs="0" maxOccurs="1"
                     default="false"/>
         <xs:element name="CtlProbeDataSize"



Niccolini, et al.       Expires February 25, 2008              [Page 32]

Internet-Draft          Traceroute Storage Format            August 2007


                     type="_CtlProbeDataSize"
                     minOccurs="0" maxOccurs="1" default="0"/>
         <xs:element name="CtlTimeOut"
                     type="_CtlTimeOut" minOccurs="0"
                     maxOccurs="1" default="3"/>
         <xs:element name="CtlProbesPerHop"
                     type="_CtlProbesPerHop"
                     minOccurs="0" maxOccurs="1" default="3"/>
         <xs:element name="CtlPort"
                     type="_CtlPort" minOccurs="0"
                     maxOccurs="1" default="33434"/>
         <xs:element name="CtlMaxTtl"
                     type="_CtlMaxTtl" minOccurs="0"
                     maxOccurs="1" default="30"/>
         <xs:element name="CtlDSField"
                     type="_CtlDSField" minOccurs="0"
                     maxOccurs="1" default="0"/>
         <xs:element name="CtlSourceAddressType"
                     type="_CtlSourceAddressType"/>



Niccolini, et al.        Expires August 26, 2007               [Page 35]

Internet-Draft          Traceroute Storage Format          February 2007
         <xs:element name="CtlSourceAddress"
                     type="_CtlSourceAddress"/>
         <xs:element name="CtlIfIndex"
                     type="_CtlIfIndex" minOccurs="0"
                     maxOccurs="1" default="0"/>
         <xs:element name="CtlMiscOptions"
                     type="_CtlMiscOptions" minOccurs="0"
                     maxOccurs="1"/>
         <xs:element name="CtlMaxFailures"
                     type="_CtlMaxFailures" minOccurs="0"
                     maxOccurs="1" default="5"/>
         <xs:element name="CtlDontFragment"
                     type="_CtlDontFragment" minOccurs="0"
                     maxOccurs="1" default="false"/>
         <xs:element name="CtlInitialTtl"
                     type="_CtlInitialTtl" minOccurs="0"
                     maxOccurs="1" default="1"/>
         <xs:element name="CtlDescr"
                     type="_CtlDescr" minOccurs="0"
                     maxOccurs="1"/>
         <xs:element name="CtlType"
                     type="_CtlType" minOccurs="0"
                     maxOccurs="1"
                     default="UDP"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_Measurement">
       <xs:annotation>



Niccolini, et al.       Expires February 25, 2008              [Page 33]

Internet-Draft          Traceroute Storage Format            August 2007


         <xs:documentation>
           Contains the actual traceroute measurement. measurement
           results.
         </xs:documentation>
       </xs:annotation>
       <xs:sequence>
         <xs:element name="TestName"
                     type="_TestName"/>
         <xs:element name="ResultsStartDateAndTime"
                     type="_ResultsStartDateAndTime"/>
         <xs:element name="ResultsIpTgtAddrType"
                     type="_ResultsIpTgtAddrType"/>
         <xs:element name="ResultsIpTgtAddr"
                     type="_ResultsIpTgtAddr"/>
         <xs:element name="ResultsProbe"
                     type="_ResultsProbe"
                     minOccurs="1" maxOccurs="2550"/>
         <xs:element name="ResultsHopRawOutputData"
                     type="_ResultsHopRawOutputData"
                     minOccurs="0" maxOccurs="255"/>



Niccolini, et al.        Expires August 26, 2007               [Page 36]

Internet-Draft          Traceroute Storage Format          February 2007
         <xs:element name="ResultsEndDateAndTime"
                     type="_ResultsEndDateAndTime"/>
       </xs:sequence>
     </xs:complexType>

     <xs:complexType name="_traceRoute">
       <xs:choice>
         <xs:sequence>
           <xs:element name="Request"
                       type="_Metadata"/>
         </xs:sequence>
         <xs:sequence>
           <xs:element name="MeasurementMetadata"
                       type="_Metadata"/>
         </xs:sequence>
         <xs:sequence>
           <xs:element name="Measurement"
                       type="_Measurement"/>
         </xs:sequence>
         <xs:sequence>
           <xs:element name="Request"
                       type="_Metadata"/>
           <xs:element name="MeasurementMetadata"
                       type="_Metadata"/>
         </xs:sequence>
         <xs:sequence>
           <xs:element name="Request"
                       type="_Metadata"/>



Niccolini, et al.       Expires February 25, 2008              [Page 34]

Internet-Draft          Traceroute Storage Format            August 2007


           <xs:element name="Measurement"
                       type="_Measurement"/>
         </xs:sequence>
         <xs:sequence>
           <xs:element name="MeasurementMetadata"
                       type="_Metadata"/>
           <xs:element name="Measurement"
                       type="_Measurement"/>
         </xs:sequence>
         <xs:sequence>
           <xs:element name="Request"
                       type="_Metadata"/>
           <xs:element name="MeasurementMetadata"
                       type="_Metadata"/>
           <xs:element name="Measurement"
                       type="_Measurement"/>
         </xs:sequence>
       </xs:choice>
     </xs:complexType>




Niccolini, et al.        Expires August 26, 2007               [Page 37]

Internet-Draft          Traceroute Storage Format          February 2007

     <!--Reference to "traceRoute" element-->
     <xs:element
      xmlns="urn:ietf:params:xml:ns:traceroute-1.0"
      name="traceRoute" type="_traceRoute"/>

   </xs:schema>



8.  Differences  Security Considerations

   Security considerations in this section discuss are grouped into
   considerations related to DISMAN-TRACEROUTE-MIB

   For performing remote conducting traceroute operations at managed node, the IETF
   has standardized the DISMAN-TRACEROUTE-MIB module in RFC 4560
   [RFC4560]. measurements and
   considerations related to storing and transmitting traceroute
   measurements information.

   This module allows:

   o  retrieving capability information memo does not specify an implementation of the a traceroute implementation
      at the managed node,
   o  configuring tool.
   Neither does it specify a certain procedure for storing traceroute operations
   measurements information.  Still it is considered desirable to be prformed,
   o  retrieving information about ongoing
   discuss related security issues below.

8.1.  Conducting Traceroute Measurements

   Conducting Internet measurements can raise both security and completed traceroute privacy
   concerns.  Traceroute measurements,
   o  retrieving traceroute measurement statistics.

   The traceroute storage format described in this document has
   significant overlaps with this MIB module.  Particularly, which traffic is injected into
   the models network, can be abused for the traceroute denial-of-service attacks disguised as
   legitimate measurement configuration and for the result from
   completed measurements are almost identical.  But for other pats of
   the DISMAN-TRACEROUTE MIB module there is no need to model them in a
   traceroute storage format.  Particularly, the capability information,
   information about ongoing measurements and measurement statistics are
   not covered by activity.




Niccolini, et al.       Expires February 25, 2008              [Page 35]

Internet-Draft          Traceroute Storage Format            August 2007


   Measurement parameters MUST be carefully selected so that the traceroute storage model.

   Concerning traceroute
   measurements and results, there are structural
   differences between the two models caused by the different choices
   for the encoding inject trivial amounts of additional traffic into the specification.  For DISMAN-TRACEROUTE-MIB,
   networks they measure.  If they inject "too much" traffic, they can
   skew the Structure results of Management Information (SMIv2, STD 58, RFC 2578
   [RFC2578]) was used, while for the traceroute storage format is
   encoded using XML.

   This difference measurement, and in structure implies that the DISMAN-TRACEROUTE-MIB
   module contains SMI-specific information element (managed objects)
   that concern tables of managed objects (specification, entry creation extreme cases cause
   congestion and delection, status retrieval) that are not required for the XML-
   encoded traceroute storage format.

   But for most of the remaining information elements that concern
   configuration denial of traceroute 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 results of completed
   measurements, treat it separately, the semantics
   measurements will not reflect actual user traffic.  If an attacker
   injects artificial traffic that is identical between accepted as legitimate, the DISMAN-
   TRACEROUTE-MIB module and loss
   rate will be artificially lowered.  Therefore, the traceroute storage format.  There are
   very few exceptions measurement
   methodologies SHOULD include appropriate techniques to this which 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.

8.2.  Securing Traceroute Measurements Information

   Traceroute measurement information are listed below.  Also naming not considered highly
   sensitive.  Still, they may contain sensitive information on network
   paths, routing states, use IP addresses, and roundtrip times, that
   the operator a networks may want to detect for business or security
   reasons.

   It is thus important to control access to Information acquired by
   conducting traceroute measurements, particularly when transmitting it
   over a networks but also when storing it.  It is RECOMMENDED that
   transmission of traceroute measurement information elements over a network
   uses appropriate protection mechanisms for preserving privacy,
   integrity and authenticity.  It is identical between both models with further RECOMMENDED that secure
   authentication and authorization are used for protecting stored
   traceroute measurement information.


9.  IANA Considerations

   This document uses URNs to describe an XML namespace and an XML
   schema for traceroute measurements information storing and
   transmission conforming to a few registry mechanism described in
   [RFC3688].  Two URI assignments are requested.
   1.  Registration request for the IPPM traceroute measurements
       namespace





Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 38] 36]

Internet-Draft          Traceroute Storage Format          February            August 2007


   exceptions.  For


       *  URI: urn:ietf:params:xml:ns:traceroute-1.0
       *  Registrant Contact: IESG
       *  XML: None.  Namespace URIs do not represent an XML
   2.  Registration request for the IPPM traceroute storage model, a few information
   elements have been added, some because of measurements schema
       *  URI: urn:ietf:params:xml:schema:traceroute-1.0
       *  Registrant Contact: IESG
       *  XML: See the different structure and
   some to provide additional information on completed measurements.

8.1.  Naming

   Basically, names in both models are chosen using the same naming
   conventions.

   For the traceroute measurement configuration information all names,
   such as CtlProbesPerHop, are identical in both models except section Section 7 of this document.


10.  References

10.1.  Normative References

   [RFC2579]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Textual Conventions for the
   traceRoute prefix that was removed to avoid unecessary redundancy in
   the XML file SMIv2",
              STD 58, RFC 2579, April 1999.

   [RFC2863]  McCloghrie, K. and F. Kastenholz, "The Interfaces Group
              MIB", RFC 2863, June 2000.

   [RFC4001]  Daniele, M., Haberman, B., Routhier, S., and J.
              Schoenwaelder, "Textual Conventions for CtlDataSize which was renamed to
   CtlProbeDataSize Internet Network
              Addresses", RFC 4001, February 2005.

   [RFC4560]  Quittek, J. and K. White, "Definitions of Managed Objects
              for clarification Remote Ping, Traceroute, and Lookup Operations",
              RFC 4560, June 2006.

10.2.  Informative References

   [I-D.ietf-ipfix-architecture]
              Sadasivan, G., "Architecture for IP Flow Information
              Export", draft-ietf-ipfix-architecture-12 (work in
              progress), September 2006.

   [I-D.ietf-ipfix-info]
              Quittek, J., "Information Model for IP Flow Information
              Export", draft-ietf-ipfix-info-15 (work in progress),
              February 2007.

   [I-D.ietf-ipfix-protocol]
              Claise, B., "Specification of the traceroute storage model.

   Results IPFIX Protocol for the
              Exchange of measurements IP Traffic Flow  Information",
              draft-ietf-ipfix-protocol-25 (work in progress),
              August 2007.

   [RFC1812]  Baker, F., "Requirements for IP Version 4 Routers",
              RFC 1812, June 1995.



Niccolini, et al.       Expires February 25, 2008              [Page 37]

Internet-Draft          Traceroute Storage Format            August 2007


   [RFC2474]  Nichols, K., Blake, S., Baker, F., and D. Black,
              "Definition of the DISMAN-TRACEROUTE-MIB modules are
   distributed over two tables, Differentiated Services Field (DS
              Field) in the traceRouteResultsTable containing
   mainly information about ongoing measurements IPv4 and the
   traceRouteProbeHistoryTable containing only information about
   completed measurements.  According to the SMIv2 naming conventions
   names IPv6 Headers", RFC 2474,
              December 1998.

   [RFC2578]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Structure of information elements in these tables have different prefixes
   (traceRouteResults Management Information
              Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC3032]  Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
              Farinacci, D., Li, T., and traceRouteProbeHistory).  Since A. Conta, "MPLS Label Stack
              Encoding", RFC 3032, January 2001.

   [RFC3410]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-
              Standard Management Framework", RFC 3410, December 2002.

   [RFC3417]  Presuhn, R., "Transport Mappings for the Simple Network
              Management Protocol (SNMP)", STD 62, RFC 3417,
              December 2002.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              January 2004.

   [XML]      Yergeau et al., F., "Extensible Markup Language (XML) 1.0
              (Third Edition)", W3C Recommendation, February 2004.


Appendix A.  Traceroute Default Configuration Parameters

   This section lists traceroute
   storage format only reports measurement configuration parameters as
   well as their defaults on completed measurements, this
   separation is not needed anymore various platforms and illustrates how
   widely they may vary.  This document considered four major traceroute
   tool implementations and compared them based on configurable
   parameters and default values.  The LINUX (SUSE 9.1), BSD (FreeBSD
   7.0) and UNIX (SunOS 5.9) implementations are based on UDP datagrams,
   while the prefix "Results" WINDOWS (XP SP2) one uses ICMP Echos.  The comparison is used for
   all related information elements.

   Beyond that, there are only a few changes
   summarized in element names.  The
   renaming actions include:

   o  traceRouteProbeHistoryProbeIndex to IndexPerHop,
   o  traceRouteProbeHistoryResponse to RoundTripTime,
   o  traceRouteProbeHistoryTime to ResultsEndDateAndTime,
   o  traceRouteProbeHistoryLastRC to ResultsHopRawOutputData.

8.2.  Semantics

   The semantics was changed for two information elements only.

   For traceRouteProbeHistoryResponse the following table, where an N/A in the DISMAN-TRACEROUTE-MIB, a
   value of 0 indicated, option column,
   means that it was such parameter is not possible to transmit a probe.
   For the traceroute strorage format, a value of 0 configurable for element
   RoundTripTime indicates that the measured time was less than one
   millisecond, while for specific
   implementation.  A comprehensive comparison of available
   implementations is outside the case that it was not possible to transmit
   a probe scope of this document; however,
   already by sampling a string is used few different implementations, it can be
   observed that indicates the problem.

   For traceRouteCtlIfIndex they can differ quite significantly in the DISMAN-TRACEROUTE-MIB, a value terms of 0
   indicated,
   configurable parameters and also default values.  Note that it in the option to set
   following table only those options which are available in at least
   two of the index is not available.
   This was translated to considered implementations are reported.

             +---------------------------------------------------------+



Niccolini, et al.       Expires February 25, 2008              [Page 38]

Internet-Draft          Traceroute Storage Format            August 2007


             |  OS    |Option|           Description         | Default |
             +--------+------+-------------------------------+---------+
             | LINUX  | -m   |Specify the maximum TTL used   |   30    |
             |--------+------|in traceroute probes.          |---------|
             | FreeBSD| -m   |                               |  OS var |
             |--------+------|                               |---------|
             | UNIX   | -m   |                               |   30    |
             |--------+------|                               |---------|
             | WINDOWS| -h   |                               |   30    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -n   |Display hop addresses          |    -    |
             |--------+------|numerically rather than        |---------|
             | FreeBSD| -n   |symbolically.                  |    -    |
             |--------+------|                               |---------|
             | UNIX   | -n   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| -d   |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -w   |Set the time to wait for a     |  3 sec  |
             |--------+------|response to a probe.           |---------|
             | FreeBSD| -w   |                               |  5 sec  |
             |--------+------|                               |---------|
             | UNIX   | -w   |                               |  5 sec  |
             |--------+------|                               |---------|
             | WINDOWS| -w   |                               |  4 sec  |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Specify a loose source route   |    -    |
             |--------+------|gateway (to direct the         |---------|
             | FreeBSD| -g   |traceroute probes through      |    -    |
             |--------+------|routers not necessarily in     |---------|
             | UNIX   | -g   | the path).                    |    -    |
             |--------+------|                               |---------|
             | WINDOWS| -g   |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -p   |Set the base UDP port number   |  33434  |
             |------- +------|used in traceroute probes      |---------|
             | FreeBSD| -p   |(UDP port = base + nhops - 1). |  33434  |
             |--------+------|                               |---------|
             | UNIX   | -p   |                               |  33434  |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -q   |Set the number of probes per   |    3    |
             |--------+------|TTL.                           |---------|
             | FreeBSD| -q   |                               |    3    |
             |--------+------|                               |---------|
             | UNIX   | -q   |                               |    3    |
             |--------+------|                               |---------|



Niccolini, et al.       Expires February 25, 2008              [Page 39]

Internet-Draft          Traceroute Storage Format            August 2007


             | WINDOWS| N/A  |                               |    3    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -S   |Set the IP source address in   |IP       |
             |--------+------|outgoing probes to the         |address  |
             | FreeBSD| -s   |specified value.               |of the   |
             |--------+------|                               |out      |
             | UNIX   | -s   |                               |interface|
             |--------+------|                               |         |
             | WINDOWS| N/A  |                               |         |
             +--------+------+-------------------------------+---------+
             | LINUX  | -t   |Set the type-of-service (TOS)  |    0    |
             |--------+------|in the probes to the specified |---------|
             | FreeBSD| -t   |value.                         |    0    |
             |--------+------|                               |---------|
             | UNIX   | -t   |                               |    0    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    0    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -v   |Verbose output: received ICMP  |    -    |
             |--------+------|packets other than             |---------|
             | FreeBSD| -v   |TIME_EXCEEDED and              |    -    |
             |--------+------|UNREACHABLE are listed.        |---------|
             | UNIX   | -v   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Set  the time (in msec) to     |    -    |
             |--------+------|pause between probes.          |---------|
             | FreeBSD| -z   |                               |    0    |
             |--------+------|                               |---------|
             | UNIX   | -P   |                               |    0    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -r   |Bypass the normal routing      |    -    |
             |--------+------|tables and send directly to a  |---------|
             | FreeBSD| -r   |host on attached network.      |    -    |
             |--------+------|                               |---------|
             | UNIX   | -r   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -f   |Set the initial TTL for the    |    1    |
             |--------+------|first probe.                   |---------|
             | FreeBSD| -f   |                               |    1    |
             |--------+------|                               |---------|
             | UNIX   | -f   |                               |    1    |
             |--------+------|                               |---------|



Niccolini, et al.       Expires February 25, 2008              [Page 40]

Internet-Draft          Traceroute Storage Format            August 2007


             | WINDOWS| N/A  |                               |    1    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -F   |Set the "don't fragment" bit.  |    -    |
             |--------+------|                               |---------|
             | FreeBSD| -F   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -F   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Enables socket level debugging.|    -    |
             |--------+------|                               |---------|
             | FreeBSD| -d   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -d   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Use ICMP ECHO instead of UDP   |    -    |
             |--------+------|datagrams.                     |---------|
             | FreeBSD| -I   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -I   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | -I   |Specify a network interface to |    -    |
             |--------+------|obtain the IP address for      |---------|
             | FreeBSD| -i   |outgoing IP packets            |    -    |
             |--------+------|(alternative to option -s).    |---------|
             | UNIX   | -i   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  | N/A  |Toggle checksum.               |    -    |
             |--------+------|                               |---------|
             | FreeBSD| -x   |                               |    -    |
             |--------+------|                               |---------|
             | UNIX   | -x   |                               |    -    |
             |--------+------|                               |---------|
             | WINDOWS| N/A  |                               |    -    |
             +--------+------+-------------------------------+---------+
             | LINUX  |  -   |As optional last parameter,    |Depends  |
             |--------+------|LINUX, FreeBSD and UNIX        |on       |
             | FreeBSD|  -   |implementations allow          |implement|
             |--------+------|specifying the traceroute strorage format, such that a probe datagram  |ation.   |
             | UNIX   |  -   |length for outgoing probes.    |         |
             |--------+------|                               |         |



Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 39] 41]

Internet-Draft          Traceroute Storage Format          February            August 2007


   value of 0 for this element indicates that


             | WINDOWS| N/A  |                               |         |
             +--------+------+-------------------------------+---------+

A.1.  Alternative Traceroute Implementations

   As stated above, the used interface is
   unknown.

   The element traceRouteProbeHistoryLastRC in widespread use of firewalls might prevent UDP or
   ICMP based traceroutes to completely trace the DISMAN-TRACEROUTE-MIB
   was replaced by element ResultsHopRawOutputData.  While
   traceRouteProbeHistoryLastRC just reports path to a reply code,
   ResultsHopRawOutputData reports the full raw output data produced by
   the destination,
   since traceroute instance that was used.

8.3.  Additional Information Elements

   Only a few information elements have been added probes might end up being filtered.  In some cases,
   such limitation might be overcome by sending instead TCP packets to
   specific ports that hosts located behind the model firewall are listening
   for connections on.  TCP based implementations use TCP SYN or FIN
   probes and listen for TIME_EXCEEDED messages, TCP RESET and other
   messages from firewalls and gateways on the path.  On the other hand,
   some firewalls filter out TCP SYN packets to prevent denial of
   service attacks, therefore the
   DISMAN-TRACEROUTE-MIB module.

   o  For providing geographical information about hops actual advantage of using TCP instead
   of UDP traceroute depends mainly on firewall configurations, which
   are not known in the advance.  A detailed analysis of TCP-based
   traceroute path, HopGeoLocation tools and measurements was added.
   o  For providing outside the top MPLS label stack entry scope of a probe in this
   document, anyway for completeness reasons the information model
   supports the storing of TCP-based traceroute path MPLSTopLabel was added.
   o  For providing additional timestamp beyond ResultsEndDateAndTime,
      ResultsStartDateAndTime and Time were added.


9.  Security Considerations

   Security considerations in this section discuss are grouped into
   considerations related to conducting measurements, too.


Appendix B.  Known Problems with Traceroute

B.1.  Compatibility between traceroute measurements and
   considerations related to storing and transmitting results and IPPM
      metrics

   Because of
   measurements.

   This memo does not specify an implementation of choices, a known inconsistency exists
   between the round-trip delay metric defined by the IPPM working group
   in RFC 2681 and the results returned by the current traceroute
   measurements.  Neither does tool
   implementations.  Unfortunately, it specify a certain procedure for
   storing is unlikely that the traceroute measurement results.  Still it
   tool implementations will implement the standard definition in the
   near future.  The only possibility is considered
   desirable therefore to discuss related security issues below.

9.1.  Conducting Traceroute Measurements

   Conducting Internet compare results of
   different traceroute measurements can raise one with each other; in order to do
   this, specifications both security of the operating system (name and privacy
   concerns.  Traceroute measurements, in which traffic is injected into version)
   and of the network, can be abused for denial-of-service attacks disguised as
   legitimate measurement activity.

   Measurement parameters MUST be carefully selected so that traceroute tool version used were added to the metadata
   elements in order to help in comparing metrics between two different
   traceroute measurements inject trivial amounts results (if run using the same operating
   system and the same version of additional traffic into the
   networks they measure.  If they inject "too much" traffic, they tool).  Moreover, the traceroute
   tool has built-in configurable mechanisms like time-outs and can
   skew
   experience problems related to the results crossing of the measurement, and in extreme cases cause
   congestion and denial firewalls; therefore
   some of service.

   The measurements themselves could the packets that traceroute sends out end up being time-out
   or filtered.  As a consequence, it might not be harmed by routers giving possible to trace the
   path to a node or there might not be a complete set of probes
   describing the RTT to reach it.






Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 40] 42]

Internet-Draft          Traceroute Storage Format          February            August 2007


   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,


Appendix C.  Differences to DISMAN-TRACEROUTE-MIB

   For performing remote traceroute operations at managed node, the
   measurements will not reflect actual user traffic.  If an attacker
   injects artificial traffic that is accepted as legitimate, IETF
   has standardized the loss
   rate will be artificially lowered.  Therefore, DISMAN-TRACEROUTE-MIB module in [RFC4560].  This
   module allows:

   o  retrieving capability information of the measurement
   methodologies SHOULD include appropriate techniques traceroute tool
      implementation at the managed node,
   o  configuring traceroute measurements to reduce be performed,
   o  retrieving information about ongoing and completed traceroute
      measurements,
   o  retrieving traceroute measurement statistics.

   The traceroute storage format described in this document has
   significant overlaps with this MIB module.  Particularly, the
   probability models
   for the traceroute measurement traffic can be distinguished configuration and for the result from "normal"
   traffic.

   Authentication techniques, such as digital signatures, may be used
   where appropriate
   completed measurements are almost identical.  But for other pats of
   the DISMAN-TRACEROUTE MIB module there is no need to guard against injected traffic attacks.

9.2.  Securing Traceroute Measurement Results

   Traceroute results model them in a
   traceroute measurements storage format.  Particularly, the capability
   information, information about ongoing measurements and measurement
   statistics are not considered highly sensible.  Still, they
   may contain sensible information on network paths, routing states,
   use IP addresses, covered by the DISMAN traceroute storage model.

   Concerning traceroute measurements and roundtrip times, that their results, there are
   structural differences between the operator a networks
   may want to detect two models caused by the different
   choices for business or security reasons.

   It is thus important to control access to the encoding of the specification.  For DISMAN-
   TRACEROUTE-MIB, the Structure of Management Information acquired by
   conducting (SMIv2, STD
   58, RFC 2578 [RFC2578]) was used, while the IPPM traceroute measurement, particularly when transmitting it
   over a networks but also when storing it.  It
   measurements data model is RECOMMENDED encoded using XML.

   This difference in structure implies that
   transmission the DISMAN-TRACEROUTE-MIB
   module contains SMI-specific information element (managed objects)
   that concern tables of traceroute measurement results over a network uses
   appropriate protection mechanisms for preserving privacy, integrity managed objects (specification, entry creation
   and authenticity.  It is further RECOMMENDED deletion, status retrieval) that secure
   authentication and authorization are used not required for protecting stored the XML-
   encoded traceroute results.


10.  IANA Considerations

   This document uses URNs to describe an XML namespace and an XML
   schema measurements data model.

   But for most of the remaining information elements that concern
   configuration of traceroute measurements conforming to a registry mechanism
   described in [RFC3688].  Two URI assignments are requested.
   1.  Registration request for and results of completed
   measurements, the semantics is identical between the DISMAN-
   TRACEROUTE-MIB module and the IPPM traceroute measurements
       namespace
       *  URI: urn:ietf:params:xml:ns:traceroute-1.0
       *  Registrant Contact: TBD.
       *  XML: None.  Namespace URIs do not represent an XML
   2.  Registration request for data model.
   There are very few exceptions to this which are listed below.  Also
   naming of information elements is identical between both models with
   a few exceptions.  For the IPPM traceroute measurements schema
       *  URI: urn:ietf:params:xml:schema:traceroute-1.0
       *  Registrant Contact: TBD.
       *  XML: See the section Section 7 data model, a few
   information elements have been added, some because of this document.


11.  References the different
   structure and some to provide additional information on completed
   measurements.






Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 41] 43]

Internet-Draft          Traceroute Storage Format          February            August 2007


11.1.  Normative References

   [RFC4001]  Daniele, M., Haberman, B., Routhier, S., and J.
              Schoenwaelder, "Textual Conventions


C.1.  Naming

   Basically, names in both models are chosen using the same naming
   conventions.

   For the traceroute measurement configuration information all names,
   such as CtlProbesPerHop, are identical in both models except for Internet Network
              Addresses", RFC 4001, February 2005.

11.2.  Informative References

   [I-D.ietf-disman-remops-mib-v2]
              Quittek, J. the
   traceRoute prefix that was removed to avoid unnecessary redundancy in
   the XML file and K. White, "Definitions of Managed Objects for Remote Ping, Traceroute, CtlDataSize which was renamed to
   CtlProbeDataSize for clarification in the traceroute measurements
   data model.

   Results of measurements in the DISMAN-TRACEROUTE-MIB modules are
   distributed over two tables, the traceRouteResultsTable containing
   mainly information about ongoing measurements and Lookup  Operations",
              draft-ietf-disman-remops-mib-v2-09 (work the
   traceRouteProbeHistoryTable containing only information about
   completed measurements.  According to the SMIv2 naming conventions
   names of information elements in progress),
              February 2006.

   [I-D.ietf-ipfix-architecture]
              Sadasivan, G., "Architecture these tables have different prefixes
   (traceRouteResults and traceRouteProbeHistory).  Since the traceroute
   measurements data model only reports on completed measurements, this
   separation is not needed anymore and the prefix "Results" is used for IP Flow Information
              Export", draft-ietf-ipfix-architecture-12 (work
   all related information elements.

   Beyond that, there are only a few changes in
              progress), September 2006.

   [I-D.ietf-ipfix-info]
              Quittek, J., "Information Model element names.  The
   renaming actions include:

   o  traceRouteProbeHistoryProbeIndex to IndexPerHop,
   o  traceRouteProbeHistoryResponse to RoundTripTime,
   o  traceRouteProbeHistoryTime to ResultsEndDateAndTime,
   o  traceRouteProbeHistoryLastRC to ResultsHopRawOutputData.

C.2.  Semantics

   The semantics was changed for IP Flow Information
              Export", draft-ietf-ipfix-info-14 (work two information elements only.

   For traceRouteProbeHistoryResponse in progress),
              October 2006.

   [I-D.ietf-ipfix-protocol]
              Claise, B., "Specification the DISMAN-TRACEROUTE-MIB, a
   value of 0 indicated, that it was not possible to transmit a probe.
   For the IPFIX Protocol traceroute measurements data model, a value of 0 for element
   RoundTripTime indicates that the
              Exchange", draft-ietf-ipfix-protocol-24 (work in
              progress), November 2006.

   [RFC1812]  Baker, F., "Requirements measured time was less than one
   millisecond, while for IP Version 4 Routers",
              RFC 1812, June 1995.

   [RFC2474]  Nichols, K., Blake, S., Baker, F., and D. Black,
              "Definition of the Differentiated Services Field (DS
              Field) case that it was not possible to transmit
   a probe a string is used that indicates the problem.

   For traceRouteCtlIfIndex in the IPv4 and IPv6 Headers", RFC 2474,
              December 1998.

   [RFC2578]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Structure DISMAN-TRACEROUTE-MIB, a value of Management Information
              Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC2579]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Textual Conventions for SMIv2",
              STD 58, RFC 2579, April 1999.

   [RFC2863]  McCloghrie, K. and F. Kastenholz, "The Interfaces Group
              MIB", RFC 2863, June 2000. 0
   indicated, that it the option to set the index is not available.
   This was translated to the traceroute measurements data model, such
   that a value of 0 for this element indicates that the used interface
   is unknown.




Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 42] 44]

Internet-Draft          Traceroute Storage Format          February            August 2007


   [RFC3032]  Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
              Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
              Encoding", RFC 3032, January 2001.

   [RFC3410]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-
              Standard Management Framework", RFC 3410, December 2002.

   [RFC3417]  Presuhn, R., "Transport Mappings for


   The element traceRouteProbeHistoryLastRC in the Simple Network
              Management Protocol (SNMP)", STD 62, RFC 3417,
              December 2002.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              January 2004.

   [RFC4560]  Quittek, J. and K. White, "Definitions DISMAN-TRACEROUTE-MIB
   was replaced by element ResultsHopRawOutputData.  While
   traceRouteProbeHistoryLastRC just reports a reply code,
   ResultsHopRawOutputData reports the full raw output data produced by
   the traceroute measurements that was used.

C.3.  Additional Information Elements

   Only a few information elements have been added to the model of Managed Objects
              for Remote Ping, Traceroute, the
   DISMAN-TRACEROUTE-MIB module.

   o  For providing geographical information about hops in the
      traceroute measurement path, HopGeoLocation was added.
   o  For providing the top MPLS label stack entry of a probe in the
      traceroute measurement path MPLSTopLabel was added.
   o  For providing additional timestamp beyond ResultsEndDateAndTime,
      ResultsStartDateAndTime and Lookup Operations",
              RFC 4560, June 2006.

   [XML]      Yergeau et al., F., "Extensible Markup Language (XML) 1.0
              (Third Edition)", W3C Recommendation, February 2004. Time were added.


Authors' Addresses

   Saverio Niccolini
   Network Laboratories, NEC Europe Ltd.
   Kurfuersten-Anlage 36
   Heidelberg  69115
   Germany

   Phone: +49 (0) 6221 4342 118
   Email: saverio.niccolini@netlab.nec.de
   URI:   http://www.netlab.nec.de


   Sandra Tartarelli
   Network Laboratories, NEC Europe Ltd.
   Kurfuersten-Anlage 36
   Heidelberg  69115
   Germany

   Phone: +49 (0) 6221 4342 132
   Email: sandra.tartarelli@netlab.nec.de
   URI:   http://www.netlab.nec.de










Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 43] 45]

Internet-Draft          Traceroute Storage Format          February            August 2007


   Juergen Quittek
   Network Laboratories, NEC Europe Ltd.
   Kurfuersten-Anlage 36
   Heidelberg  69115
   Germany

   Phone: +49 (0) 6221 4342 115
   Email: quittek@netlab.nec.de
   URI:   http://www.netlab.nec.de


   Martin Swany
   Dept. of Computer and Information Sciences, University of Delaware
   Newark  DE 19716
   U.S.A.

   Email: swany@UDel.Edu


































Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 44] 46]

Internet-Draft          Traceroute Storage Format          February            August 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Niccolini, et al.       Expires August 26, 2007 February 25, 2008              [Page 45] 47]


----