[ipfix] IPFIX WG agenda for Yokohama IETF

n.brownlee@auckland.ac.nz Wed, 03 July 2002 18: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 OAA29109 for <ipfix-archive@lists.ietf.org>; Wed, 3 Jul 2002 14:54:56 -0400 (EDT)
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 17PodZ-00044C-00 for ipfix-list@mil.doit.wisc.edu; Wed, 03 Jul 2002 13:13:57 -0500
Received: from mailhost2.auckland.ac.nz ([130.216.191.4]) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 17PodX-000441-00 for ipfix@net.doit.wisc.edu; Wed, 03 Jul 2002 13:13:55 -0500
Received: from mailhost.auckland.ac.nz (IDENT:mirapoint@mailhost [130.216.191.61]) by mailhost2.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id GAA26935 for <ipfix@net.doit.wisc.edu>; Thu, 4 Jul 2002 06:13:52 +1200 (NZST)
Received: from auckland.ac.nz (bluebottle.itss.auckland.ac.nz [130.216.4.28]) by mailhost.auckland.ac.nz (Mirapoint Messaging Server MOS 3.1.0.58-GA) with ESMTP id AFC05992; Thu, 4 Jul 2002 06:13:45 +1200 (NZST)
Message-Id: <200207031813.AFC05992@mailhost.auckland.ac.nz>
Date: Wed, 03 Jul 2002 11:12:16 -0700
From: n.brownlee@auckland.ac.nz
Subject: [ipfix] IPFIX WG agenda for Yokohama IETF
To: ipfix@net.doit.wisc.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset="us-ascii"
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>

Hello all:

The agenda for our WG meeting at the Yokohama IETF is appended below.

Cheers, Nevil

-----------------------------------------------------------------------
   Nevil Brownlee                   Director, Technology Development
   Phone: +64 9 373 7599 x8941      ITSS, The University of Auckland
   FAX: +64 9 373 7021      Private Bag 92019, Auckland, New Zealand



The IPFIX meeting at IETF 54 in Yokohama is scheduled for

    Monday afternoon, i.e. 1530-1730  on  15 July 2002

Agenda:

 1. Administriva

 2. Overview of WG charter, current status

 3. Review of WG documents, highlighing current issues, e.g.
    configuration vs some configuration (ie template uploads)
    vs no configuration.  (Document Editors)
    - Requirements
    - Architecture
    - Data Model
    - Applicability

 4. Protocol selection process (Chairs)
    At the Minneapolis meeting we reached consensus on an
    evaluation team to select the most suitable existing
    protocol for IPFIX.  The chairs will report on progress
    to date, and present a proposed evaluation timetable for
    discussion.

 5. Other items ?

Any other items, offers of short talks about experiences with
flow measurement, or anything else relevant to IPFIX, please
send email to one of the co-chairs, i.e. to Nevil Brownlee
<n.brownlee@auckland.ac.nz> or Dave Plonka <plonka@doit.wisc.edu>


Homework . . .

 * Our current published Internet Drafts are
      Requirements:  draft-ietf-ipfix-reqs-04.txt
      Architecture:  draft-ietf-ipfix-architecture-02.txt
      Data Model:    draft-ietf-ipfix-data-00.txt
      Applicability: draft-zseby-ipfix-applicability-00.txt

 * Other relevant new drafts are
      NetFlow v9:    draft-bclaise-netflow-9-00.txt

 * The IPFIX charter is at 
      http://www.ietf.org/html.charters/ipfix-charter.html

 * The IPFIX web site is
      http://www.ietf.org/html.charters/ipfix-charter.html


------------------------------------------------------------------


--
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/