RE: [ippm] traceroute as WG work item? IPFIX traceroute records

"STEPHAN Emile RD-CORE-LAN" <emile.stephan@francetelecom.com> Wed, 23 March 2005 17:34 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10503 for <ippm-archive@lists.ietf.org>; Wed, 23 Mar 2005 12:34:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DE9hL-0002lP-S0; Wed, 23 Mar 2005 12:31:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DE9hJ-0002lK-VI for ippm@megatron.ietf.org; Wed, 23 Mar 2005 12:31:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10137 for <ippm@ietf.org>; Wed, 23 Mar 2005 12:31:11 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DE9mp-0004bl-Md for ippm@ietf.org; Wed, 23 Mar 2005 12:36:56 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 23 Mar 2005 18:30:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ippm] traceroute as WG work item? IPFIX traceroute records
Date: Wed, 23 Mar 2005 18:30:19 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1F4F982@ftrdmel1.rd.francetelecom.fr>
Thread-Topic: [ippm] traceroute as WG work item? IPFIX traceroute records
Thread-Index: AcUpT+A+wm9JYVbYT+SM5xVhfYQY/gGeTYTA
From: STEPHAN Emile RD-CORE-LAN <emile.stephan@francetelecom.com>
To: Juergen Quittek <quittek@netlab.nec.de>
X-OriginalArrivalTime: 23 Mar 2005 17:30:20.0026 (UTC) FILETIME=[FC7515A0:01C52FCD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
Cc: ipfix@net.doit.wisc.edu, ippm@ietf.org
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org >
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=unsubscribe>
List-Post: <mailto:ippm@ietf.org >
List-Help: <mailto:ippm-request@ietf.org ?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=subscribe>
Sender: ippm-bounces@ietf.org
Errors-To: ippm-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Juergen,

My thinking is that we might use IPFIX to export the traceroute results.


What about using 2 templates: one for the measure and another one for results?
       
 0                   1                   2                   3  
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
|         FlowSet ID = 0        |       Length = xx bytes       |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
|               256             |       Field Length = 4        |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|    FlowID (e.g. measure ID)   |       Field Length = 4        |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| 
|    sourceIPv4Address          |      Field Length = 4         | Src 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
|  destinationIPv4Address       |        Field Length = 4       | Dst
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    

0                   1                   2                   3  
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
|         FlowSet ID = 0        |       Length = xx bytes       |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
|               257             |       Field Length = 4        |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
|    FlowID (e.g. measure ID)   |       Field Length = 4        |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
|    SampleID                   |       Field Length = 4        |  
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Src UDP 
|   flowStartMicroSeconds       |      Field Length =  8        | pkts time
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
|   flowEndDeltaUSeconds        |      Field Length =  4        | Troute RTT
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
|    destinationIPv4Address     |        Field Length = 4       | Hop Addr 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    


This is compact and is very close to what describes Guido draft (draft-pohl-perpktinfo-02.txt). 

We need only to define a new Field Type named 'SampleID' (named PacketID in Guido document).                 

Regards
Emile

-----Message d'origine-----
De : ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] De la part de Juergen Quittek
Envoyé : mardi 15 mars 2005 12:09
À : ippm@ietf.org
Objet : Re: [ippm] traceroute as WG work item?

The I-D is still missing a data model, because there is no
consensus yet on the mailing list about whether to use an
XML-based data model or a more compact one.
Please find some pro and con arguments at
http://people.internet2.edu/~matt/IPPM/Meetings/ietf62/ippm-2005-03-07-traceroute.pdf

Thanks,

    Juergen

--On 15.03.2005 11:15 +0100 Juergen Quittek wrote:

> Dear all,
>
> Unfortunately, there was no discussion on traceroute storage during
> our last meeting. Therefore I bring this issue to the mailing list.
>
> There is an I-D describing an information model for traceroute records:
> http://www.ietf.org/internet-drafts/draft-niccolini-ippm-storetraceroutes-00.txt
>
> This work was initiated by the development of a database for traffic
> measurement tools and traces, see  http://www.ist-mome.org/database/
>
> Currently, there is no standard way of exchanging traceroute
> measurements except for the DISMAN-TRACEROUTE-MIB module (RFC2925).
> But this can only be used for transferring measurement data from an
> SNMP agent to its manager(s).  It is not useful for exchange between
> traffic measurement tools.
>
> A standardized record format for traceroute measurements would be
> very useful for building tools, databases and other applications
> that handle traceroute measurements and need to exchange them.
>
> Therefore I propose that this becomes an IPPM WG work item.
> Any comment, pro or con, is very welcome.
>
> Thanks,
>
>     Juergen
> --
> Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221 90511-15
> NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 90511-55
> Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ippm



_______________________________________________
ippm mailing list
ippm@ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm

_______________________________________________
ippm mailing list
ippm@ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm