Re: [ipfix] PROPOSED list of WG items for new charter

Paul Aitken <paitken@cisco.com> Fri, 24 March 2006 01:56 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMbX3-0007NG-Qu for ipfix-archive@lists.ietf.org; Thu, 23 Mar 2006 20:56:05 -0500
Received: from mil.doit.wisc.edu ([128.104.31.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMbX3-0005oF-IP for ipfix-archive@lists.ietf.org; Thu, 23 Mar 2006 20:56:05 -0500
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 1FMbSI-0003P7-00 for ipfix-list@mil.doit.wisc.edu; Thu, 23 Mar 2006 19:51:10 -0600
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 1FMbSH-0003P0-00 for ipfix@net.doit.wisc.edu; Thu, 23 Mar 2006 19:51:09 -0600
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 24 Mar 2006 02:51:09 +0100
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k2O1p836003936 for <ipfix@net.doit.wisc.edu>; Fri, 24 Mar 2006 02:51:08 +0100 (MET)
Received: from [10.89.20.15] (rcdn-vpn-cluster-2-15.cisco.com [10.89.20.15]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id BAA17953 for <ipfix@net.doit.wisc.edu>; Fri, 24 Mar 2006 01:51:06 GMT
Message-ID: <44235088.3000005@cisco.com>
Date: Fri, 24 Mar 2006 01:51:04 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.10) Gecko/20050811 Fedora/1.7.10-1.2.1.legacy
X-Accept-Language: en-gb, en-us
MIME-Version: 1.0
To: ipfix@net.doit.wisc.edu
Subject: Re: [ipfix] PROPOSED list of WG items for new charter
References: <20060324080218.f09rbbgcuv34kwww@webmail.auckland.ac.nz>
In-Reply-To: <20060324080218.f09rbbgcuv34kwww@webmail.auckland.ac.nz>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

Nevil,

In my mind, and without prejudice to any of the authors or all their 
hard work so far, the IPFIX drafts fall into three groups:


1. Mature drafts, which can be completed soon and should be targetted 
for immediate completion:

    draft-boschi-ipfix-implementation-guidelines-01
    draft-boschi-ipfix-reducing-redundancy-01
    draft-schmoll-ipfix-testing-00

    draft-kobayashi-ipfix-concentrator-mib-01
	- this should be worked under the IPFIX MIB


2. Drafts which still require some work and should be targetted for phase 2:

    draft-dressler-ipfix-aggregation-02
    draft-bclaise-ipfix-reliability-01
    draft-trammel-ipfix-biflow-00
    draft-kobayashi-ipfix-concentrator-model-01


3. Drafts whose value I'm unconvinced of:

    draft-trammel-ipfix-file-00
    draft-stephan-isp-templates-01


> In our new charter, I propose that we take on the following as
> WG items (estimated delivery times in parenthises):
> 
> 1. IPFIX Implementation Guidelines draft, to be an Informational RFC
>       (6 months)
> 2. IPFIX Testing draft, to be an Informational RFC  (6 months)
> 3. IPFIX MIB, to be an Informational RFC (12 months)

And later you added:

> IPFIX Reducung Reduncy, to be an Informational RFC  (6 months)

I'm happy with these.


> 4  IPFIX Biflow draft, to be an Informational RFC (6 months)

In my opinion, biflow isn't sufficiently mature to be completed in 6 
months, even if it's possible to do biflow on a single box at all. I 
would prefer to see it in a second phase.


One final point: many of these drafts call for new Information Elements.

Do you feel that the processes for requesting, reviewing and approving 
new IE's have been clearly communicated to the WG?

Cheers.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

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