Re: [ipfix-eval] Some comments on the evaluation team draft

Simon Leinen <simon@limmat.switch.ch> Thu, 14 November 2002 22:54 UTC

Received: from mil.doit.wisc.edu (mil.doit.wisc.edu [128.104.31.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05042 for <ipfix-archive@lists.ietf.org>; Thu, 14 Nov 2002 17:54:19 -0500 (EST)
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 18CSms-0004Pl-00 for ipfix-list@mil.doit.wisc.edu; Thu, 14 Nov 2002 16:48:39 -0600
Received: from babar.switch.ch ([130.59.4.2]) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 18CSmq-0004Ov-00 for ipfix-eval@net.doit.wisc.edu; Thu, 14 Nov 2002 16:48:36 -0600
Received: from babar.switch.ch (localhost [IPv6:::1]) by babar.switch.ch (8.12.2+Sun/8.12.2) with ESMTP id gAEMlsKt013814; Thu, 14 Nov 2002 23:47:54 +0100 (MET)
Received: (from leinen@localhost) by babar.switch.ch (8.12.2+Sun/8.12.2/Submit) id gAEMlrLE013811; Thu, 14 Nov 2002 23:47:53 +0100 (MET)
X-Authentication-Warning: babar.switch.ch: leinen set sender to simon@limmat.switch.ch using -f
To: Benoit Claise <bclaise@cisco.com>
Cc: ipfix-eval@net.doit.wisc.edu
Subject: Re: [ipfix-eval] Some comments on the evaluation team draft
References: <3DD3C6C3.30408@cisco.com>
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7, F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR`
From: Simon Leinen <simon@limmat.switch.ch>
In-Reply-To: <3DD3C6C3.30408@cisco.com>
Date: Thu, 14 Nov 2002 23:47:53 +0100
Message-ID: <aak7jfwyxy.fsf@limmat.switch.ch>
Lines: 27
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.90
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>

On Thu, 14 Nov 2002 16:52:35 +0100, Benoit Claise <bclaise@cisco.com> said:
> 4.5 Time Synchronization  (5.5) LFAP: T     CRANE: T     IPDR: T
> NetFlow: P     Diameter: T

> In my draft
> http://www.ietf.org/internet-drafts/draft-claise-ipfix-eval-netflow-03.txt,
> I wrote

>     3.4.5 Time Synchronization (5.5)

>     _ Total Compliance. _
>     The export packet header contains the UTC time of the export packet
>     generation. This header also contains the router sysUpTime at the
>     time of the export packet generation. The UTC time the router booted
>     can therefore be deduced. The flow records contain the flow start
>     and flow end sysUpTime, so that the NetFlow collector can deduce the
>     flow start and flow end UTC time.

Yes, but the problem is (Mark Fullmer pointed this out) that the UTC
time field in the header only has 1-second resolution, so a collector
cannot convert flow timestamps to UTC times with the required
precision (centiseconds or better).

It could be fixed by making the UTC time field in the header more
precise.  I think earlier versions of NetFlow had this.
-- 
Simon.

--
Help        mailto:majordomo@net.doit.wisc.edu and say "help" in message body
Unsubscribe mailto:majordomo@net.doit.wisc.edu and say
"unsubscribe ipfix" in message body
Archive     http://ipfix.doit.wisc.edu/archive/