
From internet-drafts@ietf.org  Sun Jan  8 06:07:04 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99DB021F8594; Sun,  8 Jan 2012 06:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1JMh4ifutOVM; Sun,  8 Jan 2012 06:07:04 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1547121F8570; Sun,  8 Jan 2012 06:07:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120108140704.17736.30648.idtracker@ietfa.amsl.com>
Date: Sun, 08 Jan 2012 06:07:04 -0800
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-imix-genome-01.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 08 Jan 2012 14:07:04 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Benchmarking Methodology Working Grou=
p of the IETF.

	Title           : IMIX Genome: Specification of variable packet sizes for =
additional testing
	Author(s)       : Al Morton
	Filename        : draft-ietf-bmwg-imix-genome-01.txt
	Pages           : 9
	Date            : 2012-01-08

   Benchmarking Methodologies have always relied on test conditions with
   constant packet sizes, with the goal of understanding what network
   device capability has been tested.  Tests with constant packet size
   reveal device capabilities but differ significantly from the
   conditions encountered in operational deployment, and so additional
   tests are sometimes conducted with a mixture of packet sizes, or
   "IMIX".  The mixture of sizes a networking device will encounter is
   highly variable and depends on many factors.  An IMIX suited for one
   networking device and deployment will not be appropriate for another.
   However, the mix of sizes may be known and the tester may be asked to
   augment the fixed size tests.  To address this need, and the
   perpetual goal of specifying repeatable test conditions, this draft
   defines a way to specify the exact repeating sequence of packet sizes
   from the usual set of fixed sizes, and other forms of mixed size
   specification.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-imix-genome-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bmwg-imix-genome-01.txt


From acmorton@att.com  Sun Jan  8 07:56:32 2012
Return-Path: <acmorton@att.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09C5B21F8570 for <bmwg@ietfa.amsl.com>; Sun,  8 Jan 2012 07:56:32 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d+m-F0e-NB2m for <bmwg@ietfa.amsl.com>; Sun,  8 Jan 2012 07:56:31 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA5021F856E for <bmwg@ietf.org>; Sun,  8 Jan 2012 07:56:31 -0800 (PST)
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-5.tower-119.messagelabs.com!1326038189!9529513!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.4.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15868 invoked from network); 8 Jan 2012 15:56:29 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-5.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Jan 2012 15:56:29 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q08FuwiN019620 for <bmwg@ietf.org>; Sun, 8 Jan 2012 10:56:58 -0500
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q08Fuupd019599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Sun, 8 Jan 2012 10:56:56 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Sun, 8 Jan 2012 09:11:21 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q08EBLAX024154 for <bmwg@ietf.org>; Sun, 8 Jan 2012 09:11:21 -0500
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q08EBI9k024123 for <bmwg@ietf.org>; Sun, 8 Jan 2012 09:11:18 -0500
Message-Id: <201201081411.q08EBI9k024123@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-251-157.vpn.east.att.com[135.70.251.157](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120108140935gw100e4lkse>; Sun, 8 Jan 2012 14:09:35 +0000
X-Originating-IP: [135.70.251.157]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 08 Jan 2012 09:12:17 -0500
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
In-Reply-To: <20120108140704.17736.30648.idtracker@ietfa.amsl.com>
References: <20120108140704.17736.30648.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-imix-genome-01.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 08 Jan 2012 15:56:32 -0000

BMWG,

This update adds Ilya Varlashkin's run-length encoding suggestion
in section 5.

have a look,
Al
(as a participant)

At 09:07 AM 1/8/2012, internet-drafts@ietf.org wrote:

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories. This draft is a work item of the Benchmarking 
>Methodology Working Group of the IETF.
>
>         Title           : IMIX Genome: Specification of variable 
> packet sizes for additional testing
>         Author(s)       : Al Morton
>         Filename        : draft-ietf-bmwg-imix-genome-01.txt
>         Pages           : 9
>         Date            : 2012-01-08
>
>    Benchmarking Methodologies have always relied on test conditions with
>    constant packet sizes, with the goal of understanding what network
>    device capability has been tested.  Tests with constant packet size
>    reveal device capabilities but differ significantly from the
>    conditions encountered in operational deployment, and so additional
>    tests are sometimes conducted with a mixture of packet sizes, or
>    "IMIX".  The mixture of sizes a networking device will encounter is
>    highly variable and depends on many factors.  An IMIX suited for one
>    networking device and deployment will not be appropriate for another.
>    However, the mix of sizes may be known and the tester may be asked to
>    augment the fixed size tests.  To address this need, and the
>    perpetual goal of specifying repeatable test conditions, this draft
>    defines a way to specify the exact repeating sequence of packet sizes
>    from the usual set of fixed sizes, and other forms of mixed size
>    specification.
>
>
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-bmwg-imix-genome-01.txt
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>This Internet-Draft can be retrieved at:
>ftp://ftp.ietf.org/internet-drafts/draft-ietf-bmwg-imix-genome-01.txt
>
>_______________________________________________
>bmwg mailing list
>bmwg@ietf.org
>https://www.ietf.org/mailman/listinfo/bmwg


From janovak@cisco.com  Fri Jan 20 08:10:12 2012
Return-Path: <janovak@cisco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ECC21F863B for <bmwg@ietfa.amsl.com>; Fri, 20 Jan 2012 08:10:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36M0J8VyW2g4 for <bmwg@ietfa.amsl.com>; Fri, 20 Jan 2012 08:10:11 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 31DE721F85C5 for <bmwg@ietf.org>; Fri, 20 Jan 2012 08:10:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=janovak@cisco.com; l=10176; q=dns/txt; s=iport; t=1327075811; x=1328285411; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=UuhTbcmqu+3pEO2kyLeJMSPGALqNhq+6qSuDYwP1shg=; b=eysZPC8KA86DnHZQSypoGs3+JRCVg0EK2juBVCSD4t3byuP/eyTzN2A7 bvNdv4BqS4pQKwGKzqxhH3XI1WnFZ+Si8CYNjFm5hzb9HYp5H/mndDNTM anUzzTI5kNG444hw0EixpxbADqHPD44zCGuCjTvr1wJTPX31umCq9iLgu 8=;
X-IronPort-AV: E=Sophos;i="4.71,543,1320624000"; d="scan'208";a="127134141"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 20 Jan 2012 16:10:10 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0KGAATc013800; Fri, 20 Jan 2012 16:10:10 GMT
Received: from xmb-ams-212.cisco.com ([144.254.75.23]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 20 Jan 2012 17:10:10 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Jan 2012 17:10:07 +0100
Message-ID: <C95CC96B171AF24CA1BB6CA3C52D0BA0017DE455@XMB-AMS-212.cisco.com>
In-Reply-To: <4F149629.6020402@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: feedback on draft-ietf-bmwg-ipflow-meth-05
Thread-Index: AczUlZy6UFn1w19vSemaow46C31wBwC9xCaw
References: <4F149629.6020402@cisco.com>
From: "Jan Novak (janovak)" <janovak@cisco.com>
To: "Paul Aitken (paitken)" <paitken@cisco.com>
X-OriginalArrivalTime: 20 Jan 2012 16:10:10.0026 (UTC) FILETIME=[FBB5D4A0:01CCD78D]
Cc: Al Morton <acmorton@att.com>, IETF BMWG <bmwg@ietf.org>
Subject: Re: [bmwg] feedback on draft-ietf-bmwg-ipflow-meth-05
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 20 Jan 2012 16:10:13 -0000

Hi Paul,

Thank you for your text suggestions and language
corrections - these are always particularly valuable.

I will address your comments in the next submitted
draft version.

Jan

The climate of Edinburgh is such that the weak succumb young ....=20
and the strong envy them.
                                 Dr. Johnson



-----Original Message-----
From: Paul Aitken (paitken)=20
Sent: 16 January 2012 21:27
To: Jan Novak (janovak)
Cc: Al Morton
Subject: feedback on draft-ietf-bmwg-ipflow-meth-05

Jan,

I've finally been able to review the latest version of the draft.

I apologise that it's taken so long. Although it's late, hopefully this=20
is still useful for the WGLC which ended Jan 1st.

What few comments I have are minor. I think the draft should progress=20
swiftly now.

I'm sure Al would like to see these comments on the WG mailing list.=20
I'll wait for your feedback.

Thanks,
P.

> Internet Engineering Task Force                      Jan Novak
> Internet-Draft                                       Cisco Systems,
Inc.
> Intended status: Informational
> Expires: 7 June, 2012                                    6 December
2011
>
>           IP Flow Information Accounting and Export Benchmarking
>                                 Methodology
>                    draft-ietf-bmwg-ipflow-meth-05.txt
>
> Abstract
>
>     This document provides a methodology and framework for quantifying
>     the performance impact of monitoring of IP flows on a network
device
>     and export of this information to a collector. It identifies the
rate
>     at which the IP flows are created, expired, and successfully
exported
>     as a new performance metric in combination with traditional
>     throughput. The metric is only applicable to the devices compliant
>     with the Architecture for IP Flow Information Export [RFC5470].
>
> 2.2.5 Flow Export Rate
>
>     Definition:
>        The number of Cache entries that expire from the Cache (as
defined
>        by the Flow Expiration term) and are exported to the Collector
>        within a measurement time interval. There SHOULD NOT be any
export
>        filtering, so that all the expired cache entries are exported.
If
>        there is export filtering and it can't be disabled, this needs
to
>        be noted.
>
>        The measured Flow Export Rate MUST include *both* the Data
Stream

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
I don't think you can add emphasis like this "*both*" in an RFC.


> 4.3 Flow Monitoring Configuration
>
>     This section covers all the aspects of the Flow monitoring
>     configuration necessary on the DUT in order to perform the Flow
>     monitoring performance measurement. The necessary configuration
has
>     a number of components (see [RFC5470]), namely Observation Points,
>     Metering Process and Exporting Process as detailed below.
>
>     The DUT MUST support the Flow monitoring architecture as specified
by
>     [RFC5470]. The DUT SHOULD support IPFIX [RFC5101] to allow easier
>     results comparison due to identical export protocol architecture
when
>     using a standard.

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
Different DUTs may contain different partial IPFIX implementations, even

while claiming full IPFIX compatibility.

So I suggest, "The DUT SHOULD support IPFIX [RFC5101] to allow=20
meaningful results comparison due to the standard export protocol."


>     The DUT configuration and any existing Cache MUST be erased before
>     application of any new configuration for the currently executed
>     measurement.
>
>     4.3.2 Metering Process
>
>        The Metering Process MUST be enabled in order to create the
Cache
>        in the DUT and configure the Cache related parameters.
>
>        The Cache Size available to the DUT MUST be known and taken
into
>        account when designing the measurement as specified in section
5.
>
>        The configuration of the Metering Process MUST be reported. For

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D

s/reported/recorded/ ?


>        example, when a Flow monitoring implementation uses timeouts to
>        expire entries from the Cache, the Cache's Inactive and Active
>        Timeouts MUST be known and taken into account when designing
the
>        measurement as specified in section 5. If the Flow monitoring
>        implementation allows only timeouts equal zero (e.g. immediate

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
"equal to zero".


>        timeout or non-existent Cache) then the measurement conditions
in
>        the section 5 are fulfilled inherently without any additional

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
s/the section 5/section 5/


>        configuration. The DUT simply exports information about every
>        packet immediately.

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
Assuming there's no input or export sampling. eg, say "subject to the=20
Flow Export Rate definition in section 2.2.5 and the assumptions about=20
sampling in section 4.5.".

Or indeed, the second paragraph of 4.3.3 just below is sufficient - so=20
you could say, "subject to the Exporting Process details below".


>        If the Flow monitoring implementation allows to configure
multiple

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
s/allows to configure/allows configuration of/


>        Metering Processes on a single DUT, the exact configuration of
>        each process MUST be included in the results report. Only
>        measurements with the same number of Metering Processes can be
>        compared.
>
>        The Cache Size, the Inactive and Active Timeouts MUST be
included
>        as part of the results report.
> Novak                                                    Expires June,
2012
>                                 [Page 12]
> Internet-Draft        Flow Monitoring Benchmarking        December
2011

>
>        The Exporting Process SHOULD be configured with IPFIX [RFC5101]
as
>        the protocol to use to format the Flow Export data. If the Flow
>        monitoring implementation does not support it, proprietary

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
s/support it/support IPFIX/


>        protocols MAY be used. Only measurements with same export
protocol
>        SHOULD be compared since the protocols may differ in their
>        export efficiency.

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
Even identical protocols may use different IPFIX or NFv9 templates.

eg, there was a draft a few years ago which suggested that different=20
field orders in the exported templates were more or less efficient.

So consider noting that only exports using identical templates should be

compared - if that's not too restrictive?
ie, if templates can't be configured or the field order is fixed, then=20
that should be noted and the different field orderings recorded.


>        Various Flow monitoring implementations might use different
>        default values regarding the export of Control Information
>        [RFC5470] and therefore Flow Export corresponding to Control
>        Information SHOULD be analyzed and reported as a separate item
on
>        the measurement report. Preferably, the export of Control
>        Information SHOULD always be configured consistently across all
>        testing and configured to the minimal possible value - ideally
>        just one exported set of Control Information during each
>        measurement. Note that Control Information includes IPFIX
Options
> 4.4 Collector
>
>     The Collector is needed in order to capture the Flow Export data
>     which allows the Flow Monitoring Throughput to be measured.
>
>     The Collector can be used as exclusively capture device providing
>     just hexadecimal format of the Flow Export data. In such a case it
>     does not need to have any additional Flow Export decoding
>     capabilities and all the decoding is done off line.
>
>     However if the Collector is also used to decode the Flow Export
data
>     then it SHOULD support IPFIX [RFC5101] for easier results
analysis.

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
I don't think that using IPFIX makes the analysis any easier. However,=20
it probably makes the results more meaningful since implementations=20
should be following the same standard.

So I'd say "for meaningful results analysis."


>     If proprietary Flow Export is deployed, the Collector MUST support
it
>     otherwise the Flow Export data analysis is not possible.
>
>     The Collector MUST be capable of capturing at the full rate the
>     Active Timeout
>        Active Timeout is set (if configurable) to a value equal to or
>        higher than the Inactive Timeout. It MUST be known in order to
>        define the measurement circumstances completely and equally
>        across implementations.
>
>     Flow Keys Definition:
>        The test needs large numbers of unique Cache entries to be
created
>        by incrementing values of one or several Flow Keys. The number
of
>        unique combinations of Flow Keys values SHOULD be several times
>        larger than the DUT Cache Size. This makes sure that any
incoming
>        packet will never refresh any already existing Cache entry.
>
>     The availability of Cache Size, Inactive Timeout, Active Timeout
as
>     configuration parameters is implementation specific. If the Flow
>     monitoring implementation does not support it, the test
possibilities

=3D=3D=3D=3D=3D
PA
=3D=3D=3D=3D=3D
s/not support it/not support these parameters/


>     as specified by this document are restricted. Some testing might
be
>     viable if the implementation follows the [IPFIX-CONFIG] document
and
>     needs to be considered on the case by case basis.
>
> 5.2 Traffic Configuration
>
>     Traffic Generation
>        The traffic generator needs to increment the Flow Keys values
with
>        each sent packet, this way each packet represents one Cache
entry
>        in the DUT Cache.
>

From internet-drafts@ietf.org  Sun Jan 22 04:50:13 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D661221F8516; Sun, 22 Jan 2012 04:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z+2FVOcTjGix; Sun, 22 Jan 2012 04:50:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4264521F850D; Sun, 22 Jan 2012 04:50:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120122124957.12111.97214.idtracker@ietfa.amsl.com>
Date: Sun, 22 Jan 2012 04:49:57 -0800
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 22 Jan 2012 12:50:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Benchmarking Methodology Working Grou=
p of the IETF.

	Title           : IP Flow Information Accounting and Export Benchmarking M=
ethodology
	Author(s)       : Jan Novak
	Filename        : draft-ietf-bmwg-ipflow-meth-06.txt
	Pages           : 32
	Date            : 2012-01-22

   This document provides a methodology and framework for quantifying
   the performance impact of monitoring of IP flows on a network device
   and export of this information to a collector. It identifies the rate
   at which the IP flows are created, expired, and successfully exported
   as a new performance metric in combination with traditional
   throughput. The metric is only applicable to the devices compliant
   with the Architecture for IP Flow Information Export [RFC5470].


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-06.txt


From janovak@cisco.com  Sun Jan 22 04:54:02 2012
Return-Path: <janovak@cisco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1159221F8494 for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 04:54:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RoWqiVZ9oNgu for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 04:54:01 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCBE21F8466 for <bmwg@ietf.org>; Sun, 22 Jan 2012 04:54:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=janovak@cisco.com; l=1859; q=dns/txt; s=iport; t=1327236841; x=1328446441; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=uUi3PIgXW+AdqNbXG/m64CjtLF6D/JgJSH26GDU7LHM=; b=OIWAZ9lP9xgiOflFjfuEvJ5SHf8adE2B2VR7XfvvxvispEtVDh9xC086 8yqB1OdNBgF+pG2G9kwtbSgs7E8yFub3FGRrUCTU8+hSCYILzzlBN0Wrh O0jnnsqQCQPkz0ru2sQlVMpaF8oz2PQO74dEhhx9hRWx8x5rzUeUHAf5f c=;
X-IronPort-AV: E=Sophos;i="4.71,551,1320624000"; d="scan'208";a="127247536"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 22 Jan 2012 12:54:00 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0MCs09N011865; Sun, 22 Jan 2012 12:54:00 GMT
Received: from xmb-ams-212.cisco.com ([144.254.75.23]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 22 Jan 2012 13:53:59 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 22 Jan 2012 13:53:58 +0100
Message-ID: <C95CC96B171AF24CA1BB6CA3C52D0BA001868247@XMB-AMS-212.cisco.com>
In-Reply-To: <20120122124957.12111.97214.idtracker@ietfa.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
Thread-Index: AczZBGdb0l2pVAp9QO2jMB9FhlyYdQAAGFpA
References: <20120122124957.12111.97214.idtracker@ietfa.amsl.com>
From: "Jan Novak (janovak)" <janovak@cisco.com>
To: "Al Morton" <acmorton@att.com>
X-OriginalArrivalTime: 22 Jan 2012 12:53:59.0925 (UTC) FILETIME=[E9027250:01CCD904]
Cc: "Paul Aitken \(paitken\)" <paitken@cisco.com>, bmwg@ietf.org
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 22 Jan 2012 12:54:02 -0000

Hi,
I have just posted a new version addressing
the comments from the latest review.

Jan

The climate of Edinburgh is such that the weak succumb young ....=20
and the strong envy them.
                                 Dr. Johnson


-----Original Message-----
From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org
Sent: 22 January 2012 12:50
To: i-d-announce@ietf.org
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Benchmarking Methodology
Working Group of the IETF.

	Title           : IP Flow Information Accounting and Export
Benchmarking Methodology
	Author(s)       : Jan Novak
	Filename        : draft-ietf-bmwg-ipflow-meth-06.txt
	Pages           : 32
	Date            : 2012-01-22

   This document provides a methodology and framework for quantifying
   the performance impact of monitoring of IP flows on a network device
   and export of this information to a collector. It identifies the rate
   at which the IP flows are created, expired, and successfully exported
   as a new performance metric in combination with traditional
   throughput. The metric is only applicable to the devices compliant
   with the Architecture for IP Flow Information Export [RFC5470].


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-06.txt

_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www.ietf.org/mailman/listinfo/bmwg

From acmorton@att.com  Sun Jan 22 06:27:00 2012
Return-Path: <acmorton@att.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F56F21F844C for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 06:27:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.807
X-Spam-Level: 
X-Spam-Status: No, score=-104.807 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_05=-1.11, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2v02jJrS0rG for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 06:27:00 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id F0F8B21F8449 for <bmwg@ietf.org>; Sun, 22 Jan 2012 06:26:59 -0800 (PST)
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-7.tower-119.messagelabs.com!1327242418!11852724!1
X-Originating-IP: [144.160.128.153]
X-StarScan-Version: 6.4.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14005 invoked from network); 22 Jan 2012 14:26:58 -0000
Received: from sbcsmtp9.sbc.com (HELO flpi408.enaf.ffdc.sbc.com) (144.160.128.153) by server-7.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Jan 2012 14:26:58 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q0MEQvIR000420 for <bmwg@ietf.org>; Sun, 22 Jan 2012 06:26:57 -0800
Received: from fflint02.pst.cso.att.com (fflint02.pst.cso.att.com [150.234.39.62]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q0MEQqcc032736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Sun, 22 Jan 2012 06:26:53 -0800
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint02.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Sun, 22 Jan 2012 06:07:41 -0800
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q0MEQUWN018242 for <bmwg@ietf.org>; Sun, 22 Jan 2012 09:26:30 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q0MEQNZb018146 for <bmwg@ietf.org>; Sun, 22 Jan 2012 09:26:23 -0500
Message-Id: <201201221426.q0MEQNZb018146@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-184-116.vpn.mwst.att.com[135.70.184.116](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120122142427gw100e4lere>; Sun, 22 Jan 2012 14:24:28 +0000
X-Originating-IP: [135.70.184.116]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 22 Jan 2012 09:27:22 -0500
To: "Jan Novak (janovak)" <janovak@cisco.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <C95CC96B171AF24CA1BB6CA3C52D0BA001868247@XMB-AMS-212.cisco .com>
References: <20120122124957.12111.97214.idtracker@ietfa.amsl.com> <C95CC96B171AF24CA1BB6CA3C52D0BA001868247@XMB-AMS-212.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
Cc: "Paul Aitken \(paitken\)" <paitken@cisco.com>, bmwg@ietf.org
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 22 Jan 2012 14:27:00 -0000

At 07:53 AM 1/22/2012, Jan Novak (janovak) wrote:
>I have just posted a new version addressing
>the comments from the latest review.

Thanks, Jan.

Please have a final look everyone, I think we may be done here.

regards,
Al
bmwg chair


From paitken@cisco.com  Sun Jan 22 09:35:54 2012
Return-Path: <paitken@cisco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42AE421F8533 for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 09:35:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.28
X-Spam-Level: 
X-Spam-Status: No, score=-10.28 tagged_above=-999 required=5 tests=[AWL=0.319,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wU2jjNvY8ZjT for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 09:35:53 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3389C21F853C for <bmwg@ietf.org>; Sun, 22 Jan 2012 09:35:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=paitken@cisco.com; l=1262; q=dns/txt; s=iport; t=1327253753; x=1328463353; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=jvTN/Rcy4QvNOtjx9lfj4kvLHu1/DceVWEVSWXo1GzE=; b=Pn1x+wrXSdBqMp07VXp3hX6LjT24XUkXsMAQpk3GUi/Ro+D7FXE0W5A4 /unSQLfHOc5fEvAMIBNMoqRy+x9M0QoFHkwLenfeodHP6dagXHRsTrpdy 0kFTdTksEpxjKjNBQD6HKbrU+jla7N7e7TqyLWMn+hjsEbc1XHxEh9fh1 M=;
X-IronPort-AV: E=Sophos;i="4.71,552,1320624000"; d="scan'208";a="64310296"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 22 Jan 2012 17:35:52 +0000
Received: from [10.61.98.151] (dhcp-10-61-98-151.cisco.com [10.61.98.151]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q0MHZpq6010408; Sun, 22 Jan 2012 17:35:52 GMT
Message-ID: <4F1C48F8.7020402@cisco.com>
Date: Sun, 22 Jan 2012 17:35:52 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Lightning/1.0b2 Thunderbird/3.1.16
MIME-Version: 1.0
To: "Jan Novak (janovak)" <janovak@cisco.com>, Al Morton <acmorton@att.com>
References: <20120122124957.12111.97214.idtracker@ietfa.amsl.com> <C95CC96B171AF24CA1BB6CA3C52D0BA001868247@XMB-AMS-212.cisco.com>
In-Reply-To: <C95CC96B171AF24CA1BB6CA3C52D0BA001868247@XMB-AMS-212.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: bmwg@ietf.org
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 22 Jan 2012 17:35:54 -0000

Jan,

Thanks for the revised draft.

I have three minor editorial comments arising from the additional edits 
you made.
These could potentially be handled in the AUTH48 review. See below.


Al,

I'm happy to approve this draft. Thanks to Jan for all his hard work and 
patience.


P.



In 4.3.6, please re-add the deleted "a":

   "The MPLS forwarding performance document [RFC5695] specifies a number"
                                                                 ^


In 4.5, where you change the text to:

     "situations without packet, flow or export sampling",

Please use a serial (Oxford) comma to avoid ambiguity: "situations 
without packet, flow, or export sampling",

See http://en.wikipedia.org/wiki/Serial_comma#Ambiguity



Immediately above section 5.2, please re-add the deleted "the":

     "if the implementation follows the [IPFIX-CONFIG] document"
                                    ^^^




On 22/01/12 12:53, Jan Novak (janovak) wrote:
> Hi,
> I have just posted a new version addressing
> the comments from the latest review.
>
> Jan
>
> The climate of Edinburgh is such that the weak succumb young ....
> and the strong envy them.
>                                   Dr. Johnson


From janovak@cisco.com  Sun Jan 22 09:40:00 2012
Return-Path: <janovak@cisco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECC521F8537 for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 09:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ah37eGYZbjMg for <bmwg@ietfa.amsl.com>; Sun, 22 Jan 2012 09:39:59 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3033221F8533 for <bmwg@ietf.org>; Sun, 22 Jan 2012 09:39:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=janovak@cisco.com; l=1759; q=dns/txt; s=iport; t=1327253999; x=1328463599; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=OT64vGrKPJDU9Yq2Cng1JOgtYEpI3vAMRDJ0MqdrOJU=; b=JisNH+2pzePeI5qwtVlQMuieUri5Q6+kySEz1fYXsCXCAHR3qMJK1T0t foJ7OL6Rp/DSwApI+y0rrsVYZA6YAc8ca1oN6z1FmZ1HxEKPSOSHbOArk 3pB7sBB/OXYzQ9WTyX0V/xJ+7jE0Xgd6tPaaxEScUgWhYiYXLc/Rl+/Jc 4=;
X-IronPort-AV: E=Sophos;i="4.71,552,1320624000"; d="scan'208";a="127257867"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Jan 2012 17:39:57 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q0MHdv0O010695; Sun, 22 Jan 2012 17:39:57 GMT
Received: from xmb-ams-212.cisco.com ([144.254.75.23]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 22 Jan 2012 18:39:57 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 22 Jan 2012 18:39:33 +0100
Message-ID: <C95CC96B171AF24CA1BB6CA3C52D0BA001868273@XMB-AMS-212.cisco.com>
In-Reply-To: <4F1C48F8.7020402@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
Thread-Index: AczZLEta+ByjeFfgR8KwAKjbFDqkJAAACeIA
References: <20120122124957.12111.97214.idtracker@ietfa.amsl.com> <C95CC96B171AF24CA1BB6CA3C52D0BA001868247@XMB-AMS-212.cisco.com> <4F1C48F8.7020402@cisco.com>
From: "Jan Novak (janovak)" <janovak@cisco.com>
To: "Paul Aitken (paitken)" <paitken@cisco.com>, "Al Morton" <acmorton@att.com>
X-OriginalArrivalTime: 22 Jan 2012 17:39:57.0706 (UTC) FILETIME=[DBD80EA0:01CCD92C]
Cc: bmwg@ietf.org
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 22 Jan 2012 17:40:00 -0000

Hi,
Ok, great - I removed those when doing
ID Nits to get the correct line lengths
without formatting pages again :-) ...

Jan

The climate of Edinburgh is such that the weak succumb young ....=20
and the strong envy them.
                                 Dr. Johnson



-----Original Message-----
From: Paul Aitken (paitken)=20
Sent: 22 January 2012 17:36
To: Jan Novak (janovak); Al Morton
Cc: bmwg@ietf.org
Subject: Re: I-D Action: draft-ietf-bmwg-ipflow-meth-06.txt

Jan,

Thanks for the revised draft.

I have three minor editorial comments arising from the additional edits=20
you made.
These could potentially be handled in the AUTH48 review. See below.


Al,

I'm happy to approve this draft. Thanks to Jan for all his hard work and

patience.


P.



In 4.3.6, please re-add the deleted "a":

   "The MPLS forwarding performance document [RFC5695] specifies a
number"
                                                                 ^


In 4.5, where you change the text to:

     "situations without packet, flow or export sampling",

Please use a serial (Oxford) comma to avoid ambiguity: "situations=20
without packet, flow, or export sampling",

See http://en.wikipedia.org/wiki/Serial_comma#Ambiguity



Immediately above section 5.2, please re-add the deleted "the":

     "if the implementation follows the [IPFIX-CONFIG] document"
                                    ^^^




On 22/01/12 12:53, Jan Novak (janovak) wrote:
> Hi,
> I have just posted a new version addressing
> the comments from the latest review.
>
> Jan
>
> The climate of Edinburgh is such that the weak succumb young ....
> and the strong envy them.
>                                   Dr. Johnson


From internet-drafts@ietf.org  Mon Jan 30 10:12:12 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD21521F864B; Mon, 30 Jan 2012 10:12:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cIb+eRzkDthu; Mon, 30 Jan 2012 10:12:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD9B21F8633; Mon, 30 Jan 2012 10:12:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120130181209.31525.60230.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jan 2012 10:12:09 -0800
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-07.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 30 Jan 2012 18:12:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Benchmarking Methodology Working Grou=
p of the IETF.

	Title           : IP Flow Information Accounting and Export Benchmarking M=
ethodology
	Author(s)       : Jan Novak
	Filename        : draft-ietf-bmwg-ipflow-meth-07.txt
	Pages           : 32
	Date            : 2012-01-30

   This document provides a methodology and framework for quantifying
   the performance impact of monitoring of IP flows on a network device
   and export of this information to a collector. It identifies the rate
   at which the IP flows are created, expired, and successfully exported
   as a new performance metric in combination with traditional
   throughput. The metric is only applicable to the devices compliant
   with the Architecture for IP Flow Information Export [RFC5470].


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-07.txt

