Re: [IPFIX] IETF 81: New work for IPFIX ...
Benoit Claise <bclaise@cisco.com> Mon, 20 June 2011 13:34 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 901DE1F0C50 for <ipfix@ietfa.amsl.com>; Mon, 20 Jun 2011 06:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZP-M1xoH7LD for <ipfix@ietfa.amsl.com>; Mon, 20 Jun 2011 06:34:56 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 983C91F0C44 for <ipfix@ietf.org>; Mon, 20 Jun 2011 06:34:55 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5KDNUfl000382; Mon, 20 Jun 2011 15:23:30 +0200 (CEST)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5KDNS5i019214; Mon, 20 Jun 2011 15:23:29 +0200 (CEST)
Message-ID: <4DFF49D0.2020506@cisco.com>
Date: Mon, 20 Jun 2011 15:23:28 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Nevil Brownlee <n.brownlee@auckland.ac.nz>
References: <4DFECECB.4010000@auckland.ac.nz>
In-Reply-To: <4DFECECB.4010000@auckland.ac.nz>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [IPFIX] IETF 81: New work for IPFIX ...
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 13:34:56 -0000
Hi Nevil, > > Hi all: > > It looks as though the flow-selection draft will be ready to submit > before the Quebec IETF meeting, so it's time to start discussion > on new charter items. Looking back at the minutes from IETF 80 in > Prague, possible items are: > > 1. New versions of the base standards, 5101 and 5102, which implement > small changes that did not affect interoperation, (for example > adding detail where there are gaps in 5101) as a Standards Track > successor to 5101. Once that had been published as an RFC > for some time we could work on moving it to Draft; that should be > possible in a reasonably short time. > > 2. IE Doctors, a draft that "lays out the ground rules for developing > new IPFIX Information Elements, and clarifies how the IE Registry > process works." The issues here are > a. Should we develop an 'IE Guidelines' draft? > b. Do we want to have an 'IE Doctors' team (with IESG overview), > an expanded group of IE Expert reviewers, or what? > > 3. IPFIX Aggregation. This seems (to me) to be a required function > for IPFIX Mediation. > > 4. IPFIX Mediation protocol draft. > > 5. Exporting MIB variables using IPFIX draft. > > For any of these that we adopt as new work items, I'd like to know > - who is prepared to work on writing/editing? (at least 2 people) I'm ready to do so for all drafts. Regards, Benoit. > - who is prepared to review these drafts as they change from time > to time? (at least three people) > If you are prepared to do either of these, please email me a list > of which item numbers in the list above you're willing to write/edit > and/or to review. > > So, do please send your comments on these to the list, so that we > can have an informed discussion in Quebec City. > > Cheers, Nevil (IPFIX co-chair) >
- [IPFIX] IETF 81: New work for IPFIX ... Nevil Brownlee
- Re: [IPFIX] IETF 81: New work for IPFIX ... Benoit Claise
- Re: [IPFIX] IETF 81: New work for IPFIX ... ATSUSHI KOBAYASHI