IETF Logo Mail Archive

Re: [bmwg] Descriptive paragraph on flow export benchmarking

Al Morton <acmorton@att.com> Mon, 01 February 2010 15:08 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 6A03F28C173 for <bmwg@core3.amsl.com>; Mon, 1 Feb 2010 07:08:40 -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 2Z4aoxFWHQeQ for <bmwg@core3.amsl.com>; Mon, 1 Feb 2010 07:08:39 -0800 (PST)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id E4ADB28C0F8 for <bmwg@ietf.org>; Mon, 1 Feb 2010 07:08:20 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-2.tower-120.messagelabs.com!1265036933!30911681!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 1549 invoked from network); 1 Feb 2010 15:08:54 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-2.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Feb 2010 15:08:54 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o11F91Fi009598 for <bmwg@ietf.org>; Mon, 1 Feb 2010 10:09:01 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o11F8sE1009378 for <bmwg@ietf.org>; Mon, 1 Feb 2010 10:08:54 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o11F8kFe020134 for <bmwg@ietf.org>; Mon, 1 Feb 2010 10:08:46 -0500
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o11F8gXN020073 for <bmwg@ietf.org>; Mon, 1 Feb 2010 10:08:43 -0500
Message-Id: <201002011508.o11F8gXN020073@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-186-45.vpn.mwst.att.com[135.70.186.45](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20100201150842gw100m6bdme>; Mon, 1 Feb 2010 15:08:42 +0000
X-Originating-IP: [135.70.186.45]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 01 Feb 2010 10:08:37 -0500
To: Benoit Claise <bclaise@cisco.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <4B66D6C1.4060901@cisco.com>
References: <201001291502.o0TF2IsY014891@klpd017.kcdc.att.com> <4B66D6C1.4060901@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [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: Mon, 01 Feb 2010 15:08:40 -0000

I like it, the goal has a better flow...

Other comments?

Al
bmwg chair

At 08:27 AM 2/1/2010, Benoit Claise wrote:
>Al,
>
>What about this?
>
>Flow Export and Collection: Develop terminology and methods to
>characterize network devices flow monitoring, export, and collection.
>The goal is a methodology to assess the maximum IP flow rate that a
>network device can sustain without losing any IP flow information or
>compromising the accuracy of information exported on the IP flows,
>and to asses the forwarding plane performance (if the forwarding 
>function is present)
>in the presence of  Flow Monitoring.
>
>Regards, Jan and Benoit

v2.23.0 | Report a Bug | By Email