[ipfix-eval] draft-leinen-ipfix-eval-contrib-00.txt
Simon Leinen <simon@limmat.switch.ch> Mon, 28 October 2002 13:17 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 IAA07415 for <ipfix-archive@lists.ietf.org>; Mon, 28 Oct 2002 08:17:39 -0500 (EST)
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 1869XX-0002zz-00 for ipfix-list@mil.doit.wisc.edu; Mon, 28 Oct 2002 07:02:43 -0600
Received: from babar.switch.ch ([130.59.4.2]) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 1869XQ-0002z3-00 for ipfix-eval@net.doit.wisc.edu; Mon, 28 Oct 2002 07:02:36 -0600
Received: from babar (localhost [IPv6:::1]) by babar.switch.ch (8.12.2+Sun/8.12.2) with ESMTP id g9SD1xGU028365; Mon, 28 Oct 2002 14:01:59 +0100 (MET)
From: Simon Leinen <simon@limmat.switch.ch>
Message-ID: <15805.13639.378299.410135@limmat.switch.ch>
Date: Mon, 28 Oct 2002 14:01:59 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="WL2A9/a8g0"
Content-Transfer-Encoding: 7bit
To: ipfix-eval@net.doit.wisc.edu
Subject: [ipfix-eval] draft-leinen-ipfix-eval-contrib-00.txt
X-Mailer: VM 7.07 under Emacs 21.2.90.1
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`
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>
I decided to submit an updated version of my "Individual Evaluation"
I-D for reference, because it contains some rationale that is missing
from the first version of the evaluation team I-D. Since I hadn't
submitted the first version to the I-D repository, I had to change the
title rather than the serial number. Full text is attached.
Changes from the first version (which had been circulated on the
ipfix-eval mailing list) include:
Changed name from draft-leinen-ipfix-eval-00.txt to
draft-leinen-ipfix-eval-contrib-00.txt.
Added text about benefit/cost of split reporting à la LFAP.
Added text about benefits of server-selected byte ordering à la
CRANE.
Added text about LFAP's multi-record encoding.
Added text about NetFlow v9's periodical reporting requirement for
option and template data, and how this could be relaxed for
reporting asynchronous events, in particular when a reliable
transport is used.
(Opinionated Conclusions): Removed entire section.
(Acknowledgements): New section.
(References): Completed LFAP-MIB reference.
--
Simon.