[bmwg] Descriptive paragraph on flow export benchmarking
Al Morton <acmorton@att.com> Fri, 29 January 2010 15:02 UTC
Return-Path: <acmorton@att.com>
X-Original-To: bmwg@core3.amsl.com
Delivered-To: bmwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B6D83A67DA for <bmwg@core3.amsl.com>; Fri, 29 Jan 2010 07:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.796
X-Spam-Level:
X-Spam-Status: No, score=-105.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFAt2f52o1cH for <bmwg@core3.amsl.com>; Fri, 29 Jan 2010 07:02:07 -0800 (PST)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id C0C723A67AC for <bmwg@ietf.org>; Fri, 29 Jan 2010 07:02:07 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-4.tower-167.messagelabs.com!1264777348!20115992!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 12297 invoked from network); 29 Jan 2010 15:02:29 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-4.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Jan 2010 15:02:29 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o0TF2Mlj021876 for <bmwg@ietf.org>; Fri, 29 Jan 2010 10:02:22 -0500
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o0TF2HOC021759 for <bmwg@ietf.org>; Fri, 29 Jan 2010 10:02:17 -0500
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id o0TF2Nwt015005 for <bmwg@ietf.org>; Fri, 29 Jan 2010 09:02:23 -0600
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id o0TF2IsY014891 for <bmwg@ietf.org>; Fri, 29 Jan 2010 09:02:19 -0600
Message-Id: <201001291502.o0TF2IsY014891@klpd017.kcdc.att.com>
Received: from acmt.att.com (vpn-135-70-180-238.vpn.mwst.att.com[135.70.180.238](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20100129150218gw100m6b7fe>; Fri, 29 Jan 2010 15:02:18 +0000
X-Originating-IP: [135.70.180.238]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 29 Jan 2010 10:02:21 -0500
To: "bmwg@ietf.org" <bmwg@ietf.org>
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [bmwg] Descriptive paragraph on flow export benchmarking
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2010 15:02:08 -0000
BMWG, At our interim meeting, we suspended the discussion of flow export benchmarking with the goals to work out how we would include this work in our charter and reach consensus on the detailed discussion points raised. To get things going again, let me suggest a starting paragraph to describe this work area (below) for future re-chartering. To pick-up where the discussion stopped, please see the meeting notes http://home.comcast.net/~acmacm/BMWG/BMWG-Int-Meet.html (see item 2. in the Detailed Notes) Please make your comments on the bmwg-list. regards, Al bmwg chair * Flow Export and Collection: Develop terms and methods to characterize the both the flow monitoring characteristics of network devices. The goal is a methodology to assess the maximum IP flow rate that a network device can sustain without reducing the performance of the forwarding plane (in the case of multipurpose routing and monitoring devices), and without losing any IP flow information or compromising the accuracy of information exported on the IP flows.
- [bmwg] Descriptive paragraph on flow export bench… Al Morton
- Re: [bmwg] Descriptive paragraph on flow export b… Jan Novak (janovak)
- Re: [bmwg] Descriptive paragraph on flow export b… Benoit Claise
- Re: [bmwg] Descriptive paragraph on flow export b… Al Morton