Re: some thoughts in prep for Wed. WG meeting (was "Re: [ipfix] IPFIX WG Agenda for IETF 52")
Dave Plonka <plonka@doit.wisc.edu> Tue, 11 December 2001 16:51 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 LAA20312 for <ipfix-archive@lists.ietf.org>; Tue, 11 Dec 2001 11:51:09 -0500 (EST)
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 16Dpnc-0001lF-00 for ipfix-list@mil.doit.wisc.edu; Tue, 11 Dec 2001 10:30:32 -0600
Received: from dplonka by mil.doit.wisc.edu with local (Exim 3.13 #1) id 16Dpna-0001l7-00; Tue, 11 Dec 2001 10:30:30 -0600
Date: Tue, 11 Dec 2001 10:30:30 -0600
From: Dave Plonka <plonka@doit.wisc.edu>
To: ipfix@net.doit.wisc.edu
Cc: Juergen Quittek <quittek@ccrle.nec.de>
Subject: Re: some thoughts in prep for Wed. WG meeting (was "Re: [ipfix] IPFIX WG Agenda for IETF 52")
Message-ID: <20011211103030.A5635@doit.wisc.edu>
Reply-To: plonka@doit.wisc.edu
References: <20011210190231.B16189@doit.wisc.edu> <3026382177.1008048729@BETA>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <3026382177.1008048729@BETA>; from quittek@ccrle.nec.de on Tue, Dec 11, 2001 at 05:32:09AM +0100
Organization: UW-Madison, DoIT, Network Services
X-VMS-Error: %SYSTEM-F-SUBRNG6, subscript 6 range error, PC=00000000, PS=0000059C
X-Shakespearean-Insult: Thou spleeny clay-brained lewdster
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>
On Tue, Dec 11, 2001 at 05:32:09AM +0100, Juergen Quittek wrote: > --On 10 December 2001 19:02 -0600 Dave Plonka <plonka@doit.wisc.edu> wrote: > > 0) add "Definitions" section (1.2?) <snip> > I agree, that this is a very helpful extension of the document. > When we submitted the current draft, we already had a "terminology" > or "definitions" section on our to do list for the next version. > > What should probably be added is > f) observation point Yes, I'm not sure I understand the use of that term yet. > Do you suggest to rename "measuring device" by "exporter"? In short, yes. We can discuss this in the meeting and summarize the proposal to the list following the meeting tomorrow (Dec 11). > > 1) Unidirectional vs. bi-directional flow definition > > This will be an interesting discussion. Agreed - I'll leave it at that until the meeting minutes. <snip> > > 2) In what ways might the exporter adapt/deal with copious amounts of > > data... > > dynamic timeouts? > > dynamic flow rules? > > dynamic sampling on/off? > > You do not mention the most obvious option: > stop measuring? Yes, that is a fair addition to stop exporting, or stop exporting flows of a particular type. I'm not trying to list all options, I just want to introduce the idea so that we can explore how the Requirements I-D might allow the exporter to change its behavior "on the fly" due to resource and bandwidth limitations, perhaps as configured. Interestingly, "draft-duffield-framework-papame-00" mentions some of these issues. For those that haven't looked at it, it has a lot of issues in common with our effort. Dave -- plonka@doit.wisc.edu http://net.doit.wisc.edu/~plonka ARS:N9HZF Madison, WI -- 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/
- some thoughts in prep for Wed. WG meeting (was "R… Dave Plonka
- Re: some thoughts in prep for Wed. WG meeting (wa… Juergen Quittek
- [ipfix] Some ideas on IPFIX-architecture Kevin Zhang
- Re: some thoughts in prep for Wed. WG meeting (wa… Benoit Claise
- [ipfix] Re: some thoughts in prep for Wed. WG mee… Robert Lowe
- Re: some thoughts in prep for Wed. WG meeting (wa… Dave Plonka