
From acmorton@att.com  Tue Apr  3 19:29:45 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 0ED7C11E80E8 for <bmwg@ietfa.amsl.com>; Tue,  3 Apr 2012 19:29:45 -0700 (PDT)
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 N0JRKiYFGfYp for <bmwg@ietfa.amsl.com>; Tue,  3 Apr 2012 19:29:44 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 5FEC911E8072 for <bmwg@ietf.org>; Tue,  3 Apr 2012 19:29:39 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 312bb7f4.0.997163.00-472.2769146.nbfkord-smmo03.seg.att.com (envelope-from <acmorton@att.com>);  Wed, 04 Apr 2012 02:29:39 +0000 (UTC)
X-MXL-Hash: 4f7bb21354b283ee-a013378bbce35c3543066ed237d7c02f4c627ebd
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 q342TcYJ011477 for <bmwg@ietf.org>; Tue, 3 Apr 2012 22:29:38 -0400
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 q342TaoI011461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Tue, 3 Apr 2012 22:29:36 -0400
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>; Tue, 3 Apr 2012 22:29:16 -0400
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 q342TEph019622 for <bmwg@ietf.org>; Tue, 3 Apr 2012 22:29:14 -0400
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 q342T8qp019428 for <bmwg@ietf.org>; Tue, 3 Apr 2012 22:29:08 -0400
Message-Id: <201204040229.q342T8qp019428@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-255-196.vpn.east.att.com[135.70.255.196](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120404022615gw1004orsie>; Wed, 4 Apr 2012 02:26:16 +0000
X-Originating-IP: [135.70.255.196]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 03 Apr 2012 22:30:16 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.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
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=1cakRACOHqwA:10 a=rDvz41e5248A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=1IPBwVEfI7SliPqXvCoA:9 a=]
X-AnalysisOut: [CjuIK1q_8ugA:10 a=5PQjMxyL9KoA:10]
Subject: [bmwg] Draft Minutes for IETF-83 Session
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: Wed, 04 Apr 2012 02:29:45 -0000

BMWG,

Visit
http://www.ietf.org/proceedings/83/minutes/minutes-83-bmwg.html
to review the draft minutes.

comments to me or the list,
Al
bmwg chair


From acmorton@att.com  Sat Apr  7 08:02:45 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 0451F21F8554 for <bmwg@ietfa.amsl.com>; Sat,  7 Apr 2012 08:02:45 -0700 (PDT)
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 K6f4Z1FEEY0M for <bmwg@ietfa.amsl.com>; Sat,  7 Apr 2012 08:02:44 -0700 (PDT)
Received: from nbfkord-smmo04.seg.att.com (nbfkord-smmo04.seg.att.com [209.65.160.86]) by ietfa.amsl.com (Postfix) with ESMTP id AC12D21F84D8 for <bmwg@ietf.org>; Sat,  7 Apr 2012 08:02:28 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo04.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 307508f4.0.2345811.00-246.6495550.nbfkord-smmo04.seg.att.com (envelope-from <acmorton@att.com>);  Sat, 07 Apr 2012 15:02:28 +0000 (UTC)
X-MXL-Hash: 4f805704712eea7f-3c2553db0e05c07813b4ea6ad50b96b0e2a9a13b
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 q37F2RLG025804 for <bmwg@ietf.org>; Sat, 7 Apr 2012 11:02:27 -0400
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 q37F2L2v025740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Sat, 7 Apr 2012 11:02:23 -0400
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>; Sat, 7 Apr 2012 11:01:49 -0400
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 q37F1lkl004213 for <bmwg@ietf.org>; Sat, 7 Apr 2012 11:01:49 -0400
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 q37F1iFs004026 for <bmwg@ietf.org>; Sat, 7 Apr 2012 11:01:45 -0400
Message-Id: <201204071501.q37F1iFs004026@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-168-135.vpn.mwst.att.com[135.70.168.135](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120407145847gw1004or30e>; Sat, 7 Apr 2012 14:58:48 +0000
X-Originating-IP: [135.70.168.135]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 07 Apr 2012 11:02:53 -0400
To: bmwg@ietf.org, fred@cisco.com
From: Al Morton <acmorton@att.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
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=cHeZH_CE8OwA:10 a=1PvKYzv9x6sA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=BqEg4_3jAAAA:8 a=AUd_NHdV]
X-AnalysisOut: [AAAA:8 a=79T-Y-kUtu5_9aLyCmIA:9 a=CjuIK1q_8ugA:10 a=lZB815]
X-AnalysisOut: [dzVvQA:10 a=1eQkaoUQ5BgA:10 a=JfD0Fch1gWkA:10]
Subject: [bmwg] Fwd: RFC 6556 on Testing Eyeball Happiness
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: Sat, 07 Apr 2012 15:02:45 -0000

Congrats, Fred. Glad we could help!

Al
bmwg chair


>To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>Subject: RFC 6556 on Testing Eyeball Happiness
>From: rfc-editor@rfc-editor.org
>Date: Fri,  6 Apr 2012 14:12:03 -0700 (PDT)
>Cc: rfc-editor@rfc-editor.org
>X-BeenThere: ietf-announce@ietf.org
>X-Mailman-Version: 2.1.12
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 6556
>
>         Title:      Testing Eyeball Happiness
>         Author:     F. Baker
>         Status:     Informational
>         Stream:     IETF
>         Date:       April 2012
>         Mailbox:    fred@cisco.com
>         Pages:      10
>         Characters: 23727
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-baker-bmwg-testing-eyeball-happiness-05.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc6556.txt
>
>The amount of time it takes to establish a session using common
>transport APIs in dual-stack networks and networks with filtering
>such as proposed in BCP 38 is a barrier to IPv6 deployment.  This
>note describes a test that can be used to determine whether an
>application can reliably establish sessions quickly in a complex
>environment such as dual-stack (IPv4+IPv6) deployment or IPv6
>deployment with multiple prefixes and upstream ingress filtering.
>This test is not a test of a specific algorithm, but of the external
>behavior of the system as a black box.  Any algorithm that has the
>intended external behavior will be accepted by it.  This document is
>not an Internet Standards Track specification; it is
>published for informational purposes.
>


From fred@cisco.com  Sat Apr  7 11:12:22 2012
Return-Path: <fred@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 43D8C21F84D8 for <bmwg@ietfa.amsl.com>; Sat,  7 Apr 2012 11:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 9IAVYQ01F7-J for <bmwg@ietfa.amsl.com>; Sat,  7 Apr 2012 11:12:21 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9FED721F84B8 for <bmwg@ietf.org>; Sat,  7 Apr 2012 11:12:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1866; q=dns/txt; s=iport; t=1333822341; x=1335031941; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=uPyWmYvG+ce89mJTEWSFYbW9VGJU4Bhav9EQZFvLyxw=; b=aVD+J1hRkzsq1BSjb4KeSVwAFoiIaRSeSUMzSXgVNm2PprjCqgqENGWn XO1i6kQds8zyf6L2ODr0zZEK4mOe1q+TX6lwa+g+xbuOYtr0DF5XzXoFE s3XvfIMyM1lsR8qhR7Gk1lZTTWoXFW22axnd0+a1rtiixWfoflUADaxk6 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EABSDgE+rRDoG/2dsb2JhbABDuS+BB4IJAQEBAwESASc/BQsLDgMDAQIvTwgGEyKHZwQMnlqXVYsrhExjBIhajRKFcohbgWmDB4E8
X-IronPort-AV: E=Sophos;i="4.75,387,1330905600"; d="scan'208";a="39517648"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 07 Apr 2012 18:12:21 +0000
Received: from stealth-10-32-244-222.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q37IC3BS002393; Sat, 7 Apr 2012 18:12:20 GMT
Received: from [127.0.0.1] by stealth-10-32-244-222.cisco.com (PGP Universal service); Sat, 07 Apr 2012 11:12:21 -0700
X-PGP-Universal: processed; by stealth-10-32-244-222.cisco.com on Sat, 07 Apr 2012 11:12:21 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <201204071501.q37F1iq6004024@alpd052.aldc.att.com>
Date: Sat, 7 Apr 2012 11:11:37 -0700
Message-Id: <FDB0B60C-1A0C-4B09-A3E6-3E15721387E7@cisco.com>
References: <201204071501.q37F1iq6004024@alpd052.aldc.att.com>
To: Al Morton <acmorton@att.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: bmwg@ietf.org
Subject: Re: [bmwg] RFC 6556 on Testing Eyeball Happiness
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: Sat, 07 Apr 2012 18:12:22 -0000

Thanks much! Your help was excellent, and much appreciated.

On Apr 7, 2012, at 8:02 AM, Al Morton wrote:

> Congrats, Fred. Glad we could help!
> 
> Al
> bmwg chair
> 
> 
>> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>> Subject: RFC 6556 on Testing Eyeball Happiness
>> From: rfc-editor@rfc-editor.org
>> Date: Fri,  6 Apr 2012 14:12:03 -0700 (PDT)
>> Cc: rfc-editor@rfc-editor.org
>> X-BeenThere: ietf-announce@ietf.org
>> X-Mailman-Version: 2.1.12
>> 
>> A new Request for Comments is now available in online RFC libraries.
>> 
>> 
>>        RFC 6556
>> 
>>        Title:      Testing Eyeball Happiness
>>        Author:     F. Baker
>>        Status:     Informational
>>        Stream:     IETF
>>        Date:       April 2012
>>        Mailbox:    fred@cisco.com
>>        Pages:      10
>>        Characters: 23727
>>        Updates/Obsoletes/SeeAlso:   None
>> 
>>        I-D Tag:    draft-baker-bmwg-testing-eyeball-happiness-05.txt
>> 
>>        URL:        http://www.rfc-editor.org/rfc/rfc6556.txt
>> 
>> The amount of time it takes to establish a session using common
>> transport APIs in dual-stack networks and networks with filtering
>> such as proposed in BCP 38 is a barrier to IPv6 deployment.  This
>> note describes a test that can be used to determine whether an
>> application can reliably establish sessions quickly in a complex
>> environment such as dual-stack (IPv4+IPv6) deployment or IPv6
>> deployment with multiple prefixes and upstream ingress filtering.
>> This test is not a test of a specific algorithm, but of the external
>> behavior of the system as a black box.  Any algorithm that has the
>> intended external behavior will be accepted by it.  This document is
>> not an Internet Standards Track specification; it is
>> published for informational purposes.
>> 
> 


From acmorton@att.com  Mon Apr  9 09:32:05 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 454D321F872F for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 09:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.479
X-Spam-Level: 
X-Spam-Status: No, score=-101.479 tagged_above=-999 required=5 tests=[AWL=-1.741, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_51=0.6, MIME_HTML_ONLY=1.457, MSGID_FROM_MTA_HEADER=0.803, 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 QzMjZxwQEez4 for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 09:32:04 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id D37FE21F8627 for <bmwg@ietf.org>; Mon,  9 Apr 2012 09:31:58 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id efe038f4.0.298207.00-466.807731.nbfkord-smmo05.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 09 Apr 2012 16:31:58 +0000 (UTC)
X-MXL-Hash: 4f830efe35255b79-669a86b97dae9f1d1eca98e39b0aea37ef8df7fe
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 q39GVvJW020736 for <bmwg@ietf.org>; Mon, 9 Apr 2012 12:31:58 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q39GVp4R020667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Mon, 9 Apr 2012 12:31:53 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Mon, 9 Apr 2012 12:31:18 -0400
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 q39GVHRu014977 for <bmwg@ietf.org>; Mon, 9 Apr 2012 12:31:18 -0400
Received: from mailgw1.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 q39GVGYF014952 for <bmwg@ietf.org>; Mon, 9 Apr 2012 12:31:16 -0400
Message-Id: <201204091631.q39GVGYF014952@alpd052.aldc.att.com>
Received: from acmt.att.com (martym.mt.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120409162818gw1004or3qe>; Mon, 9 Apr 2012 16:28:18 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 09 Apr 2012 12:32:23 -0400
To: "Aamer Akhter (aakhter)" <aakhter@cisco.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <7F298ACC76CC154F832B6D02852D169F079F3DC7@XMB-RCD-101.cisco .com>
References: <7F298ACC76CC154F832B6D02852D169F079F3DC7@XMB-RCD-101.cisco.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-RSA-Inspected: yes
X-RSA-Classifications: public, General SSNFP Patterns
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=B446KA1xWiEA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=zQP7CpKOAAAA:8 a=AUd_NHdVAAAA:8 a=48vgC7mU]
X-AnalysisOut: [AAAA:8 a=jGqiy6jZAAAA:8 a=rPVc2femCYqE9y9UPOoA:9 a=l08AvCe]
X-AnalysisOut: [wyP3_-EFama4A:7 a=CjuIK1q_8ugA:10 a=_W_S_7VecoQA:10 a=Hz7I]
X-AnalysisOut: [rDYlS0cA:10 a=JfD0Fch1gWkA:10 a=lZB815dzVvQA:10]
Cc: bmwg@ietf.org
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: Mon, 09 Apr 2012 16:32:05 -0000

<html>
<body>
At 03:24 AM 3/28/2012, Aamer Akhter (aakhter)
wrote:<blockquote type=cite class=cite cite="">
<dl>
<dd>Hi Al,<br><br>

<dd>:-)&nbsp;I don't have a strong opinion against the indirect
reference.<br>

<dd>My preference would be to be more direct about it and perhaps even a
<dd>mention of IPFIX as a scalable way to gather this data in private
<dd>networks. </blockquote>
</dl><br>
OK, what if we say:<br><br>
...<br>
The mixture of sizes a networking device will encounter is highly<br>
variable and depends on many factors. An IMIX suited for one
networking<br>
device and deployment will not be appropriate for another.<br>
However, the mix of sizes may be known and the tester may be asked
to<br>
augment the fixed size tests. The references above cite the original<br>
studies and their methodologies. Similar methods can be used to<br>
determine new size mixes present on a link or network. We note that<br>
the architecture for IP Flow Information Export [RFC5470] provides<br>
one method to gather packet size information on private
networks.<br><br>
Are there any other canonical ipfix RFCs that should also be
listed?<br><br>
Al<br><br>
<br><br>
<br><br>
<blockquote type=cite class=cite cite="">-------- Original Message
--------<br>
Subject: <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Re: I-D
Action: draft-ietf-bmwg-imix-genome-01.txt<br>
Date: <x-tab>&nbsp;&nbsp;</x-tab>Tue, 27 Mar 2012 10:23:09 -0400<br>
From: <x-tab>&nbsp;&nbsp;</x-tab>Al Morton &lt;acmorton@att.com&gt;<br>
To: <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Aamer Akhter (aakhter)
&lt;aakhter@cisco.com&gt;<br>
CC: <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>bmwg@ietf.org<br>
Newsgroups: <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>gmane.ietf.bmwg<br>
References:
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>
&lt;20120108140704.17736.30648.idtracker@ietfa.amsl.com&gt;<br>
&lt;4F71ACFC.5080706@cisco.com&gt;<br>
&lt;7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco.com&gt;<br>
&lt;7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco
.com&gt;<br><br>
<br><br>
At 08:10 AM 3/27/2012, Aamer Akhter (aakhter) wrote:<br>
&gt; Al,<br>
&gt;<br>
&gt; Just following up on the quick discussion on the live meeting at
<br>
&gt; IETF-83 regarding the creation of a representative the IMIX:<br>
&gt;<br>
&gt; A cntrl+f search against CAIDA didn't turn up any matches.<br>
&gt; Perhaps this got lost in the editing<br><br>
Turns out that the CAIDA study is an indirect Reference, see
below:<br><br>
1. Introduction<br><br>
...<br>
Streams of constant packet size differ significantly from the
conditions<br>
encountered in operational deployment, and so additional tests are<br>
sometimes conducted with a mixture of packet sizes. The set of sizes<br>
used is often called an Internet Mix, or &quot;IMIX&quot;<br>
[Spirent], [IXIA], [Agilent].<br><br>
The mixture of sizes a networking device will encounter is highly<br>
variable and depends on many factors. An IMIX suited for one
networking<br>
device and deployment will not be appropriate for another.<br>
However, the mix of sizes may be known and the tester may be asked
to<br>
augment the fixed size tests. The references above cite the original<br>
studies and their methodologies - *similar methods can be used to<br>
determine new size mixes.<br><br>
*hope that does it,<br>
Al<br>
_______________________________________________<br>
bmwg mailing list<br>
bmwg@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/bmwg" eudora="autourl">
https://www.ietf.org/mailman/listinfo/bmwg</a></blockquote></body>
</html>


From aakhter@cisco.com  Mon Apr  9 10:56:35 2012
Return-Path: <aakhter@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 73B7F21F8427 for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 10:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.998
X-Spam-Level: 
X-Spam-Status: No, score=-109.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_HI=-8, 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 cjwPgrFH+plV for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 10:56:33 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id E75B221F84FF for <bmwg@ietf.org>; Mon,  9 Apr 2012 10:56:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=aakhter@cisco.com; l=10787; q=dns/txt; s=iport; t=1333994193; x=1335203793; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=MXQYUHKJ5DL54OyaN9HfRnwyNHt7re4roE5LrWrZdKw=; b=G8SqzrrzJD133Aome7JHhR2RP/QONSj0TQ/bqRVyNvM4vO3Hp7Z/x93M Fh7RnNBo0Mn/k5OWKmmSVlumJCo1trAZH9Cnp6XEA+jgkMWSPEZQFVw2M WaDxbFyyUcMpzV/08nEvbWER8x86es76k03/H2tGYs/iOwoxSKyT3ann5 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAJMig0+tJV2a/2dsb2JhbABEgka2ZIEHggkBAQEEAQEBDwEJEQM+CwwEAgEIDgMBAgEBAQEKBhcBBgEmHwMGCAEBBBMIGodsC5l7oAAEj3djBIham1+BaYMF
X-IronPort-AV: E=Sophos;i="4.75,393,1330905600"; d="scan'208,217";a="73180912"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 09 Apr 2012 17:56:32 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q39HuVxR014963;  Mon, 9 Apr 2012 17:56:32 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 9 Apr 2012 12:56:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD167A.1232BAC2"
Date: Mon, 9 Apr 2012 12:56:18 -0500
Message-ID: <7F298ACC76CC154F832B6D02852D169F07BB84FE@XMB-RCD-101.cisco.com>
In-Reply-To: <201204091631.q39GVGiD014953@alpd052.aldc.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [bmwg] I-D Action: draft-ietf-bmwg-imix-genome-01.txt
Thread-Index: Ac0WbkkV6RVe/mEoRUeAJfVRCfbWWwAC7yJA
References: <7F298ACC76CC154F832B6D02852D169F079F3DC7@XMB-RCD-101.cisco.com> <201204091631.q39GVGiD014953@alpd052.aldc.att.com>
From: "Aamer Akhter (aakhter)" <aakhter@cisco.com>
To: "Al Morton" <acmorton@att.com>
X-OriginalArrivalTime: 09 Apr 2012 17:56:21.0235 (UTC) FILETIME=[124B2C30:01CD167A]
Cc: bmwg@ietf.org
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: Mon, 09 Apr 2012 17:56:35 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD167A.1232BAC2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Al-this is fine.=20

=20

I think the existing RFC reference is ok as well.=20

=20

From: Al Morton [mailto:acmorton@att.com]=20
Sent: Monday, April 09, 2012 12:32 PM
To: Aamer Akhter (aakhter)
Cc: bmwg@ietf.org
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-imix-genome-01.txt

=20

At 03:24 AM 3/28/2012, Aamer Akhter (aakhter) wrote:

Hi Al,

:-) I don't have a strong opinion against the indirect reference.

My preference would be to be more direct about it and perhaps even a=20

mention of IPFIX as a scalable way to gather this data in private=20

networks.=20


OK, what if we say:

...
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. The references above cite the original
studies and their methodologies. Similar methods can be used to
determine new size mixes present on a link or network. We note that
the architecture for IP Flow Information Export [RFC5470] provides
one method to gather packet size information on private networks.

Are there any other canonical ipfix RFCs that should also be listed?

Al








-------- Original Message --------
Subject:        Re: I-D Action: draft-ietf-bmwg-imix-genome-01.txt
Date:   Tue, 27 Mar 2012 10:23:09 -0400
From:   Al Morton <acmorton@att.com>
To:     Aamer Akhter (aakhter) <aakhter@cisco.com>
CC:     bmwg@ietf.org
Newsgroups:     gmane.ietf.bmwg
References:      <20120108140704.17736.30648.idtracker@ietfa.amsl.com>
<4F71ACFC.5080706@cisco.com>
<7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco.com>
<7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco .com
<mailto:7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco%20.co
m> >



At 08:10 AM 3/27/2012, Aamer Akhter (aakhter) wrote:
> Al,
>
> Just following up on the quick discussion on the live meeting at=20
> IETF-83 regarding the creation of a representative the IMIX:
>
> A cntrl+f search against CAIDA didn't turn up any matches.
> Perhaps this got lost in the editing

Turns out that the CAIDA study is an indirect Reference, see below:

1. Introduction

...
Streams of constant packet size differ significantly from the conditions
encountered in operational deployment, and so additional tests are
sometimes conducted with a mixture of packet sizes. The set of sizes
used is often called an Internet Mix, or "IMIX"
[Spirent], [IXIA], [Agilent].

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. The references above cite the original
studies and their methodologies - *similar methods can be used to
determine new size mixes.

*hope that does it,
Al
_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www.ietf.org/mailman/listinfo/bmwg


------_=_NextPart_001_01CD167A.1232BAC2
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks Al&#8212;this is fine. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I think the existing RFC reference is ok as well. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Al Morton [mailto:acmorton@att.com] <br><b>Sent:</b> Monday, April 09, =
2012 12:32 PM<br><b>To:</b> Aamer Akhter (aakhter)<br><b>Cc:</b> =
bmwg@ietf.org<br><b>Subject:</b> Re: [bmwg] I-D Action: =
draft-ietf-bmwg-imix-genome-01.txt<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>At 03:24 AM =
3/28/2012, Aamer Akhter (aakhter) wrote:<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;mar=
gin-left:.5in'>Hi Al,<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'>:-)&nbsp;I don't have a strong opinion =
against the indirect reference.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'>My preference would be to be more direct =
about it and perhaps even a <o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'>mention of IPFIX as a scalable way to gather =
this data in private <o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'>networks. <o:p></o:p></p><p =
class=3DMsoNormal><br>OK, what if we say:<br><br>...<br>The mixture of =
sizes a networking device will encounter is highly<br>variable and =
depends on many factors. An IMIX suited for one networking<br>device and =
deployment will not be appropriate for another.<br>However, the mix of =
sizes may be known and the tester may be asked to<br>augment the fixed =
size tests. The references above cite the original<br>studies and their =
methodologies. Similar methods can be used to<br>determine new size =
mixes present on a link or network. We note that<br>the architecture for =
IP Flow Information Export [RFC5470] provides<br>one method to gather =
packet size information on private networks.<br><br>Are there any other =
canonical ipfix RFCs that should also be =
listed?<br><br>Al<br><br><br><br><br><br><br><o:p></o:p></p><p =
class=3DMsoNormal>-------- Original Message --------<br>Subject: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Re: I-D Action: =
draft-ietf-bmwg-imix-genome-01.txt<br>Date: &nbsp;&nbsp;Tue, 27 Mar 2012 =
10:23:09 -0400<br>From: &nbsp;&nbsp;Al Morton &lt;<a =
href=3D"mailto:acmorton@att.com">acmorton@att.com</a>&gt;<br>To: =
&nbsp;&nbsp;&nbsp;&nbsp;Aamer Akhter (aakhter) &lt;<a =
href=3D"mailto:aakhter@cisco.com">aakhter@cisco.com</a>&gt;<br>CC: =
&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"mailto:bmwg@ietf.org">bmwg@ietf.org</a><br>Newsgroups: =
&nbsp;&nbsp;&nbsp;&nbsp;gmane.ietf.bmwg<br>References: =
&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a =
href=3D"mailto:20120108140704.17736.30648.idtracker@ietfa.amsl.com">20120=
108140704.17736.30648.idtracker@ietfa.amsl.com</a>&gt;<br>&lt;<a =
href=3D"mailto:4F71ACFC.5080706@cisco.com">4F71ACFC.5080706@cisco.com</a>=
&gt;<br>&lt;<a =
href=3D"mailto:7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco=
.com">7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco.com</a>&=
gt;<br>&lt;<a =
href=3D"mailto:7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco=
%20.com">7F298ACC76CC154F832B6D02852D169F078D5B82@XMB-RCD-101.cisco =
.com</a>&gt;<br><br><br><br>At 08:10 AM 3/27/2012, Aamer Akhter =
(aakhter) wrote:<br>&gt; Al,<br>&gt;<br>&gt; Just following up on the =
quick discussion on the live meeting at <br>&gt; IETF-83 regarding the =
creation of a representative the IMIX:<br>&gt;<br>&gt; A cntrl+f search =
against CAIDA didn't turn up any matches.<br>&gt; Perhaps this got lost =
in the editing<br><br>Turns out that the CAIDA study is an indirect =
Reference, see below:<br><br>1. Introduction<br><br>...<br>Streams of =
constant packet size differ significantly from the =
conditions<br>encountered in operational deployment, and so additional =
tests are<br>sometimes conducted with a mixture of packet sizes. The set =
of sizes<br>used is often called an Internet Mix, or =
&quot;IMIX&quot;<br>[Spirent], [IXIA], [Agilent].<br><br>The mixture of =
sizes a networking device will encounter is highly<br>variable and =
depends on many factors. An IMIX suited for one networking<br>device and =
deployment will not be appropriate for another.<br>However, the mix of =
sizes may be known and the tester may be asked to<br>augment the fixed =
size tests. The references above cite the original<br>studies and their =
methodologies - *similar methods can be used to<br>determine new size =
mixes.<br><br>*hope that does =
it,<br>Al<br>_______________________________________________<br>bmwg =
mailing list<br><a href=3D"mailto:bmwg@ietf.org">bmwg@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/bmwg">https://www.ietf.org/=
mailman/listinfo/bmwg</a><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CD167A.1232BAC2--

From acmorton@att.com  Mon Apr  9 11:14:39 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 CA78F21F87E3 for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 11:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.621
X-Spam-Level: 
X-Spam-Status: No, score=-101.621 tagged_above=-999 required=5 tests=[AWL=-1.283, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, MSGID_FROM_MTA_HEADER=0.803, 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 sR7rY3diaI22 for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 11:14:39 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 05BDB21F87E1 for <bmwg@ietf.org>; Mon,  9 Apr 2012 11:14:38 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id e07238f4.0.345209.00-383.943052.nbfkord-smmo05.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 09 Apr 2012 18:14:39 +0000 (UTC)
X-MXL-Hash: 4f83270f62cf6ec1-291430a6aba3f309ab6925122995f31326bb0e7e
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 q39IEc7Z008428 for <bmwg@ietf.org>; Mon, 9 Apr 2012 14:14:38 -0400
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 q39IEY1X008386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Mon, 9 Apr 2012 14:14:34 -0400
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>; Mon, 9 Apr 2012 14:14:19 -0400
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 q39IEILr003465 for <bmwg@ietf.org>; Mon, 9 Apr 2012 14:14:18 -0400
Received: from mailgw1.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 q39IEFuG003215 for <bmwg@ietf.org>; Mon, 9 Apr 2012 14:14:15 -0400
Message-Id: <201204091814.q39IEFuG003215@alpd052.aldc.att.com>
Received: from acmt.att.com (dn135-16-251-71.dhcpn.ugn.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120409181117gw1004or48e>; Mon, 9 Apr 2012 18:11:17 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 09 Apr 2012 14:15:23 -0400
To: "Aamer Akhter (aakhter)" <aakhter@cisco.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <7F298ACC76CC154F832B6D02852D169F07BB84FE@XMB-RCD-101.cisco .com>
References: <7F298ACC76CC154F832B6D02852D169F079F3DC7@XMB-RCD-101.cisco.com> <201204091631.q39GVGiD014953@alpd052.aldc.att.com> <7F298ACC76CC154F832B6D02852D169F07BB84FE@XMB-RCD-101.cisco.com>
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=B446KA1xWiEA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=tjcoHcdY9atbXh9HXmYA:9 a=wPNLvfGTeEIA:10 a]
X-AnalysisOut: [=_W_S_7VecoQA:10]
Cc: bmwg@ietf.org
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: Mon, 09 Apr 2012 18:14:39 -0000

<html>
<body>
At 01:56 PM 4/9/2012, Aamer Akhter (aakhter)
wrote:<blockquote type=3Dcite class=3Dcite cite=3D"">
<dl>
<dd>Thanks Al=97this is fine. <br>

<dd>I think the existing RFC reference is ok as well. </blockquote>
</dl><br>
So let it be written. So let it be done.<br>
Al<br>
</body>
</html>


From acmorton@att.com  Mon Apr  9 12:07:42 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 1AE0321F87B5 for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 12:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.243
X-Spam-Level: 
X-Spam-Status: No, score=-104.243 tagged_above=-999 required=5 tests=[AWL=1.553, 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 82kG07hFdZIw for <bmwg@ietfa.amsl.com>; Mon,  9 Apr 2012 12:07:41 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 34B9A21F8782 for <bmwg@ietf.org>; Mon,  9 Apr 2012 12:07:41 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id c73338f4.0.370424.00-443.1015380.nbfkord-smmo03.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 09 Apr 2012 19:07:41 +0000 (UTC)
X-MXL-Hash: 4f83337d5506f632-1bfcf230ac09cf592f8df9d09ddc2e544ade7d2c
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 q39J7dWM023556 for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:40 -0400
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 q39J7Y1I023475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:35 -0400
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>; Mon, 9 Apr 2012 15:07:25 -0400
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 q39J7OlG031591 for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:25 -0400
Received: from mailgw1.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 q39J7Gek031223 for <bmwg@ietf.org>; Mon, 9 Apr 2012 15:07:17 -0400
Message-Id: <201204091907.q39J7Gek031223@alpd052.aldc.att.com>
Received: from acmt.att.com (martym.mt.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120409190419gw1004or4ke>; Mon, 9 Apr 2012 19:04:19 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 09 Apr 2012 15:08:26 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.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
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=okYqswJ-1YkA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=nDD7OEIXCd9TiC5ZxJIA:9 a=]
X-AnalysisOut: [7RZhSPuPspECN0-hYXIA:7 a=CjuIK1q_8ugA:10 a=GbL8SpxeVU4gwMA]
X-AnalysisOut: [y:21 a=ii2CeGh184rUI45H:21]
Cc: draft-ietf-bmwg-ca-bench-meth@tools.ietf.org
Subject: [bmwg] Comments on draft-ietf-bmwg-ca-bench-meth-01
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, 09 Apr 2012 19:07:42 -0000

Mike and Sarah,

Comments below, some are purely editorial.

Al
(as a participant)

-=-=-=-=-=-=-

Section 1 Intro
...
    The end goal of this methodology is to generate performance metrics
    in a lab environment that will more closely relate to actual observed
s/more closely/closely/

    performance on production networks.  By utilizing dynamic traffic
    patterns relevant to modern networks, this methodology should be able
    to more closely tie laboratory and production metrics.
s/more closely/closely/

and a question about:
   ... It should be
    further noted than any metrics acquired from production networks
    SHOULD be captured according to the policies and procedures of the
    IPPM or PMOL working groups.

What metrics are you thinking about here?

-=-=-=-=-=-=-

Section 3.2

    ...Application Flows,
    as defined in RFC 2722 [9] are able to be well-defined without simply
    referring to a network capture.  An example traffic template is
    defined and listed in Appendix A of this document.

Actually, RFC 2722 defines a Traffic Flow, not application:

3 Traffic Flows and Reporting Granularity

    A flow was defined in section 2.1 above in abstract terms as follows:

        "A TRAFFIC FLOW is an artifical logical equivalent to a call or
        connection, belonging to a (user-specieied) METERED TRAFFIC
        GROUP."

-=-=-=-=-=-=-=-

Section 3.4
...
    If we change the example slightly and increase the size of each
    datagram to 1312 bytes, then it becomes necessary to recompute the
    math.
s/math/load/

-=-=-=-=-=-=-=-

3.7.3.  TCP Stack Considerations

    The IETF has historically provided guidance and information on TCP
    stack considerations.  This methodology is strictly focused on
    performance metrics at layers above 4, thus does not specifically
    define any TCP stack configuration parameters of either the tester or
    the DUTs.  The TCP configuration of the tester MUST remain constant
    across all DUTs in order to ensure comparable results.  While the
    following list of references is not exhaustive, each document
    contains a relevant discussion on TCP stack considerations.

    Congestion control algorithms are discussed in Section 2 of RFC 3148
    [11] with even more detailed references.  TCP receive and congestion
    window sizes are discussed in detail in RFC 6349 [12].

It would be useful to cite the TCP Raodmap in the first paragraph above:
http://tools.ietf.org/html/rfc4614


-=-=-=-=-=-=-=-=-=-

4.1.3 Procedure

It's worth noting that when the offered load results in
100% link utilization on all ingress links,
then the DUT has achieved "wire-speed performance",
or words to that effect.

...
    This procedure MAY be repeated any number of times with the results
    being averaged together.
s/number/reasonable number/

-=-=-=-=-=-=-=-=-=-

4.1.4.3.  Packet Loss

    The test tool SHOULD report the number of flow packets lost or
    dropped from source to destination.
s/flow packets/packets/ (i think)

-=-=-=-=-=-=-=-=-=-

4.2.4.5.  Packet Loss

    The test tool SHOULD report the number of flow packets lost or
    dropped from source to destination.

Remove - redundant with 4.2.4.2

-=-=-=-=-=-=-=-=-=-

4.2.4.6.  Application Flow Latency

    The test tool SHOULD report the minimum, maximum and average amount
    of time an application flow member takes to traverse the DUT, as
    defined by RFC 1242 [3], Section 3.13.

What is a "flow member"?
Are these statistics calculated over all packets in a flow?

    ...                                    This rate SHOULD be reported
    individually for each application protocol present within the traffic
    mix.

Not a rate, latency is in units of seconds.

-=-=-=-=-=-=-=-=-=-

Appendix B

Good!






From Barry.Constantine@jdsu.com  Tue Apr 10 14:08:58 2012
Return-Path: <Barry.Constantine@jdsu.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 2C51C11E8103 for <bmwg@ietfa.amsl.com>; Tue, 10 Apr 2012 14:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No, score=-5.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 wtzUzqF7TE6u for <bmwg@ietfa.amsl.com>; Tue, 10 Apr 2012 14:08:57 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with SMTP id 2417A21F8687 for <bmwg@ietf.org>; Tue, 10 Apr 2012 14:08:56 -0700 (PDT)
Received: from mx6.jdsu.com ([209.36.247.248]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKT4ShaEf+8OcIgxLl9h78zSqO23hoYoDc@postini.com; Tue, 10 Apr 2012 14:08:57 PDT
Received: from milexhtca1.ds.jdsu.net (192.168.10.158) by mx6.jdsu.com (192.168.10.248) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 10 Apr 2012 14:08:34 -0700
Received: from MILEXCH3.ds.jdsu.net ([fe80::1886:5e83:acc7:502e]) by milexhtca1.ds.jdsu.net ([::1]) with mapi; Tue, 10 Apr 2012 14:08:55 -0700
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "bmwg@ietf.org" <bmwg@ietf.org>
Date: Tue, 10 Apr 2012 14:08:53 -0700
Thread-Topic: Comments on draft-ietf-bmwg-ca-bench-meth-01.txt
Thread-Index: Ac0XXiIYlrh6MzmESj+F2UrrFXzyBA==
Message-ID: <71DE5E2C0ADA26429D102DEAC78AF5110B07C4C1C6@MILEXCH3.ds.jdsu.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_71DE5E2C0ADA26429D102DEAC78AF5110B07C4C1C6MILEXCH3dsjds_"
MIME-Version: 1.0
Subject: [bmwg] Comments on draft-ietf-bmwg-ca-bench-meth-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: Tue, 10 Apr 2012 21:08:58 -0000

--_000_71DE5E2C0ADA26429D102DEAC78AF5110B07C4C1C6MILEXCH3dsjds_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Mike / Sarah,

The document is really coming along nicely.

Here are some comments / suggestions I had:

4.1.4.3.  Packet Loss

   The test tool SHOULD report the number of flow packets lost or
   dropped from source to destination.

>>>>>>>>>>>>
   The TCP Efficiency metric from RFC 6349 could be beneficial in this area=
.
   Specifically TCP Efficiency is the ratio of:

   total transmitted bytes - retransmitted bytes
   ------------------------------------------------------  x 100
                total transmitted bytes

  Ideal score is 100%.

   With TCP based application flows, it is the number of retransmitted byte=
s
   that is more telling than the number of lost packets, and the efficiency
   metric helps to quantify the overall performance.

   So I would consider measuring packet loss and TCP Efficiency (and on a p=
er
   flow basis would be very useful as well).


 4.1.4.4.  Application Flow Latency

   The test tool SHOULD report the minimum, maximum and average amount
   of time an application flow member takes to traverse the DUT, as
   defined by RFC 1242 [3], Section 3.8.  This rate SHOULD be reported
   individually for each application protocol present within the traffic
   mix.

>>>>>>>>>>>>>>
   Similarly, the Buffer Delay Percent from RFC 6349 could be useful here.
   Buffer Delay =3D

   RTT (under load) - RTT baseline
   --------------------------------------- x 100
            RTT baseline

Ideal =3D 0%

Versus just min, max, and average, Buffer Delay percent (in combination wit=
h
TCP Efficiency) can segment performance issues into the loss related issues=
 versus
device buffering performance issues.

I was involved with a benchmark of WAN Acceleration devices recently, and t=
he
vendor found these metrics to be very beneficial for the reasons I stated a=
bove.

Thank you,
Barry Constantine



--_000_71DE5E2C0ADA26429D102DEAC78AF5110B07C4C1C6MILEXCH3dsjds_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi Mike / Sarah,=
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>The document is really coming along nicely.<o:p></o:p></p><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Here are some comments / s=
uggestions I had:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
p class=3DMsoNormal>4.1.4.3.&nbsp; Packet Loss<o:p></o:p></p><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; The test tool=
 SHOULD report the number of flow packets lost or<o:p></o:p></p><p class=3D=
MsoNormal>&nbsp;&nbsp; dropped from source to destination.<o:p></o:p></p><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt;&gt;&gt;&g=
t;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p class=3DMsoNormal=
>&nbsp;&nbsp; The TCP Efficiency metric from RFC 6349 could be beneficial i=
n this area.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; Specifically T=
CP Efficiency is the ratio of:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; total transmitted bytes - ret=
ransmitted bytes<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; ----------=
--------------------------------------------&nbsp; x 100<o:p></o:p></p><p c=
lass=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total transmitted bytes<o:p></o:p></p><p c=
lass=3DMsoNormal>&nbsp;&nbsp; <o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nb=
sp;Ideal score is 100%.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>&nbsp;&nbsp; With TCP based application flows, it=
 is the number of retransmitted bytes <o:p></o:p></p><p class=3DMsoNormal>&=
nbsp;&nbsp;&nbsp;that is more telling than the number of lost packets, and =
the efficiency<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; metric helps=
 to quantify the overall performance.<o:p></o:p></p><p class=3DMsoNormal>&n=
bsp;&nbsp; <o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;So I would=
 consider measuring packet loss and TCP Efficiency (and on a per<o:p></o:p>=
</p><p class=3DMsoNormal>&nbsp;&nbsp; flow basis would be very useful as we=
ll).<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; <o:p></o:p></p><p clas=
s=3DMsoNormal>&nbsp;&nbsp;&nbsp;<o:p></o:p></p><p class=3DMsoNormal>&nbsp;4=
.1.4.4.&nbsp; Application Flow Latency<o:p></o:p></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; The test tool SHOULD =
report the minimum, maximum and average amount<o:p></o:p></p><p class=3DMso=
Normal>&nbsp;&nbsp; of time an application flow member takes to traverse th=
e DUT, as<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; defined by RFC 12=
42 [3], Section 3.8.&nbsp; This rate SHOULD be reported<o:p></o:p></p><p cl=
ass=3DMsoNormal>&nbsp;&nbsp; individually for each application protocol pre=
sent within the traffic<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; mix=
.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal>&nbsp;&nbsp; Similarly, the Buffer Delay Percent=
 from RFC 6349 could be useful here.<o:p></o:p></p><p class=3DMsoNormal>&nb=
sp;&nbsp; Buffer Delay =3D<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;RTT (under load) - RT=
T baseline<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; ----------------=
----------------------- x 100<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RTT baseline<o:p><=
/o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p>=
</o:p></p><p class=3DMsoNormal>Ideal =3D 0%<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Versus just min, max, and ave=
rage, Buffer Delay percent (in combination with<o:p></o:p></p><p class=3DMs=
oNormal>TCP Efficiency) can segment performance issues into the loss relate=
d issues versus <o:p></o:p></p><p class=3DMsoNormal>device buffering perfor=
mance issues.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></p><=
p class=3DMsoNormal>I was involved with a benchmark of WAN Acceleration dev=
ices recently, and the<o:p></o:p></p><p class=3DMsoNormal>vendor found thes=
e metrics to be very beneficial for the reasons I stated above.<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thank you=
,<o:p></o:p></p><p class=3DMsoNormal>Barry Constantine<o:p></o:p></p><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div></body></html>=

--_000_71DE5E2C0ADA26429D102DEAC78AF5110B07C4C1C6MILEXCH3dsjds_--

From rbonica@juniper.net  Mon Apr 16 08:33:57 2012
Return-Path: <rbonica@juniper.net>
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 8A55A21F86A3 for <bmwg@ietfa.amsl.com>; Mon, 16 Apr 2012 08:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.519
X-Spam-Level: 
X-Spam-Status: No, score=-106.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, 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 HCnPKOHzdKp3 for <bmwg@ietfa.amsl.com>; Mon, 16 Apr 2012 08:33:57 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id C51EF21F86A1 for <bmwg@ietf.org>; Mon, 16 Apr 2012 08:33:56 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKT4w75ENPGFRtyw4Vs/cnUGbb0LIWsbYv@postini.com; Mon, 16 Apr 2012 08:33:56 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 16 Apr 2012 08:32:07 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 16 Apr 2012 11:32:06 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "bmwg@ietf.org" <bmwg@ietf.org>
Date: Mon, 16 Apr 2012 11:32:05 -0400
Thread-Topic: WGLC: draft-ietf-bmwg-2544-as
Thread-Index: Ac0b5hPQto5G5uFRT8GYkXqrSXrTFw==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76A4A4C4D@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [bmwg] WGLC: draft-ietf-bmwg-2544-as
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, 16 Apr 2012 15:33:57 -0000

Folks,

This concludes a WG Last Call for draft-ietf-bmwg-2544-as. Last call commen=
ts have been integrated into the draft and the chair is instructed to send =
this document to the IESG for publication.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From acmorton@att.com  Thu Apr 19 11:48:26 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 3BEEE21F865C for <bmwg@ietfa.amsl.com>; Thu, 19 Apr 2012 11:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.547
X-Spam-Level: 
X-Spam-Status: No, score=-105.547 tagged_above=-999 required=5 tests=[AWL=0.249, 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 Icx5cZ1aUWXm for <bmwg@ietfa.amsl.com>; Thu, 19 Apr 2012 11:48:25 -0700 (PDT)
Received: from nbfkord-smmo04.seg.att.com (nbfkord-smmo04.seg.att.com [209.65.160.86]) by ietfa.amsl.com (Postfix) with ESMTP id 68F7921F8655 for <bmwg@ietf.org>; Thu, 19 Apr 2012 11:48:25 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo04.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 9fd509f4.0.1715286.00-332.4767947.nbfkord-smmo04.seg.att.com (envelope-from <acmorton@att.com>);  Thu, 19 Apr 2012 18:48:25 +0000 (UTC)
X-MXL-Hash: 4f905df903fc3ec4-83445423672da4dcd041a81fe2dfc6cd39f7ab5c
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 q3JImODu025327 for <bmwg@ietf.org>; Thu, 19 Apr 2012 14:48:24 -0400
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 q3JImJCn025280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Thu, 19 Apr 2012 14:48:19 -0400
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>; Thu, 19 Apr 2012 14:47:45 -0400
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 q3JIljZh015776 for <bmwg@ietf.org>; Thu, 19 Apr 2012 14:47:45 -0400
Received: from mailgw1.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 q3JIlbeR015174 for <bmwg@ietf.org>; Thu, 19 Apr 2012 14:47:38 -0400
Message-Id: <201204191847.q3JIlbeR015174@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-206-197.vpn.east.att.com[135.70.206.197](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120419184430gw1004orpge>; Thu, 19 Apr 2012 18:44:31 +0000
X-Originating-IP: [135.70.206.197]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 19 Apr 2012 14:48:46 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.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
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=VY1BQGvZnB4A:10 a=oGaApbiJSAcA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=zQP7CpKOAAAA:8 a=w5u1Rucc]
X-AnalysisOut: [qOyATZdeDzAA:9 a=CjuIK1q_8ugA:10 a=qg_hPROt29YA:10 a=Hz7Ir]
X-AnalysisOut: [DYlS0cA:10]
Cc: "Worley, Dale R \(Dale\)" <dworley@avaya.com>
Subject: [bmwg] WGLC on SIP Benchmarking Drafts (04)
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: Thu, 19 Apr 2012 18:48:26 -0000

BMWG:

A WG Last Call period for the Internet-Drafts on SIP Device
Benchmarking:

http://www.ietf.org/id/draft-ietf-bmwg-sip-bench-term-04.txt

http://www.ietf.org/id/draft-ietf-bmwg-sip-bench-meth-04.txt

will be open from 19 April 2012 through 18 May 2012.

These drafts are continuing the BMWG Last Call Process. See
http://www1.ietf.org/mail-archive/web/bmwg/current/msg00846.html
The first WGLC was completed on 5 April 2010 with comments.

Please read and express your opinion on whether or not these
Internet-Drafts should be forwarded to the Area Directors for
publication as Informational RFCs.  Send your comments
to this list or acmorton@att.com

Al
bmwg chair 


From bmwg@wjcerveny.com  Sun Apr 22 13:29:15 2012
Return-Path: <bmwg@wjcerveny.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 E71F421F8585 for <bmwg@ietfa.amsl.com>; Sun, 22 Apr 2012 13:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 lEYlYAu1rv7d for <bmwg@ietfa.amsl.com>; Sun, 22 Apr 2012 13:29:15 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id DA4E721F8575 for <bmwg@ietf.org>; Sun, 22 Apr 2012 13:29:14 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9037C2145A for <bmwg@ietf.org>; Sun, 22 Apr 2012 16:29:14 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 22 Apr 2012 16:29:14 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:content-type :content-transfer-encoding:subject:date:message-id:to :mime-version; s=smtpout; bh=T5bVpgtNg/CzffDLwO5QEDmlmYI=; b=pRd kv1ZyIMgls8maqRoSbjmyMz4zUnUHn9joPRx9DgCu7hIYrqKGQ+nlLLj5L5UjMmK I5Elys/CP7NR+RzSYVgy5B15MRZOCzFHM7i05dxokaxVv3xLHqN/hhNfLBfI5TWA 2+zJQL5w9SAF9jP5k6xa3mSFZPnvQ7pNlzG9FZME=
X-Sasl-enc: VQ3IypxnY+4k5LZ/ZZCxTbvJvfl9s7WG1HmNPg3OK/e5 1335126554
Received: from [10.1.14.64] (unknown [204.181.64.8]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4E5B14827C6 for <bmwg@ietf.org>; Sun, 22 Apr 2012 16:29:14 -0400 (EDT)
From: Bill Cerveny <bmwg@wjcerveny.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sun, 22 Apr 2012 16:31:19 -0400
Message-Id: <90865B1A-BE86-4C77-AE3D-5813A45767AC@wjcerveny.com>
To: bmwg@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [bmwg] Document writeup for draft-ietf-bmwg-2544-as-02
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 Apr 2012 20:29:16 -0000

Below is the document write-up for draft-ietf-bmwg-2544-as-02, "RFC 2544 =
Applicability Statement: Use on Production Networks Considered Harmful", =
which has been submitted for publication.

Regards,

Bill Cerveny
Document Shepherd for draft-ietf-bmwg-2544-as-02=20

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

   Informational, as indicated on the title page.
   All BMWG RFCs are traditionally Informational,
   in part because they do not define protocols and
   the traditional conditions for standards track advancement
   did not apply.  However, they are specifications and
   the RFC 2119 terms are applicable to identify the
   level of requirements.

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

   Benchmarking Methodology Working Group (BMWG) has been developing key
   performance metrics and laboratory test methods since 1990, and
   continues this work at present.  Recent application of the methods
   beyond their intended scope is cause for concern.  This memo
   clarifies the scope of RFC 2544 and other benchmarking work for the
   IETF community.

Working Group Summary

   Working group consensus was achieved in a single WGLC, after allowing
   a year for review and many useful comments and exchanges.=20

Document Quality

   The single-sentence message of this memo was clear from first =
publication.
   Most comments helped to make the wording more concise.

Personnel

  Document Shepherd: Bill Cerveny <wcerveny@wjcerveny.com>

  Area Director: Ronald Bonica <rbonica@juniper.net>

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

   The document shepherd has reviewed this document three times.  There =
are no
   outstanding issues, as far as the document shepherd is concerned.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed? =20

   No

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

   No

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

   There are no specific concerns or issues that the document shepherd
   has with this document.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

   Each author has confirmed that there are no known IPR concerns, nor
   are any IPR disclosures required.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

   No

(9) How solid is the WG consensus behind this document? Does it=20
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it?  =20=


   Many WG members have reviewed this draft, including long-time =
participants,
   new participants, and (most importantly) participants who work at =
companies
   most affected by the statements in this memo. WG consensus was called
   by Area Director Ron Bonica, since the current chair and *all past =
chairs*
   are co-authors.

(10) Has anyone threatened an appeal or otherwise indicated extreme=20
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)=20

   No appeals have been threatened.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

   ID nits have been checked.  There was only one nit identified and =
this=20
   appears to be an error. This one id nit complained about addresses=20
   falling within "non-RFC5735-compliant IPv4 addresses" As far as I can=20=

   tell, the only addresses are in section 4.2 and these are exactly =
within=20
   the range described in RFC5735.

   The tools team has been notified as this appears to be a bug or error =
in=20
   the nits checking program.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

   Not applicable

(13) Have all references within this document been identified as
either normative or informative?

   Yes

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

   No

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in =
the
Last Call procedure.=20

   No

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

   No

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

   There are no IANA considerations.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

   None

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

   Not applicable.=

From internet-drafts@ietf.org  Mon Apr 23 12:45:46 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 F1D2621F8582; Mon, 23 Apr 2012 12:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 Wf5hrcBo-OsK; Mon, 23 Apr 2012 12:45:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF98621F850C; Mon, 23 Apr 2012 12:45:44 -0700 (PDT)
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: 4.00
Message-ID: <20120423194544.21682.42610.idtracker@ietfa.amsl.com>
Date: Mon, 23 Apr 2012 12:45:44 -0700
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-ipflow-meth-10.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, 23 Apr 2012 19:45:46 -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-10.txt
	Pages           : 33
	Date            : 2012-04-23

   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]. The
   methodology quantifies the impact of the IP flow monitoring process
   on the network equipment.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ipflow-meth-10.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-10.txt


From iesg-secretary@ietf.org  Mon Apr 23 14:11:09 2012
Return-Path: <iesg-secretary@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 ECD1011E8088; Mon, 23 Apr 2012 14:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 WwxahWNipi-x; Mon, 23 Apr 2012 14:11:08 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A2611E808A; Mon, 23 Apr 2012 14:11:07 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.01
Message-ID: <20120423211107.7675.47479.idtracker@ietfa.amsl.com>
Date: Mon, 23 Apr 2012 14:11:07 -0700
Cc: bmwg chair <bmwg-chairs@tools.ietf.org>, bmwg mailing list <bmwg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [bmwg] Document Action: 'IP Flow Information Accounting and Export	Benchmarking Methodology' to Informational RFC	(draft-ietf-bmwg-ipflow-meth-10.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, 23 Apr 2012 21:11:09 -0000

The IESG has approved the following document:
- 'IP Flow Information Accounting and Export Benchmarking Methodology'
  (draft-ietf-bmwg-ipflow-meth-10.txt) as an Informational RFC

This document is the product of the Benchmarking Methodology Working
Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-bmwg-ipflow-meth/




     Technical Summary 
For internetworking devices that perform routing or switching as 
their primary function, the likely reduction in traffic-handling
capacity when traffic monitoring is active continues to be a relevant 
question many years after it was first asked ("What happens when you
turn-on Netflow?"). 

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].

The methods are applicable to both internetworking devices that 
forward traffic and other devices that simply monitor traffic with 
non-intrusive access to transmission facilities.
The Forwarding Plane and Monitoring Plane represent two separate
functional blocks, each with its own performance capability. The
Forwarding Plane handles user data packets and is fully characterised 
by the metrics defined by [RFC2544]. 
The Monitoring Plane handles Flows which reflect the analysed 
traffic. The metric for Monitoring Plane performance is Flow Export 
Rate, and the benchmark is the Flow Monitoring Throughput.


     Working Group Summary 
Quite a few bmwg participants and ipfix participants have given this a look
and now concur with the results. 
Examples of Test Implementation and Results were presented 
during development, which is compelling evidence of practicality.
There were WGLCs yielding long lists of comments/issues to deal with, 
and this was finally accomplished. It took several WGLCs before this version
reached consensus (with a few minor editorial changes).  
 

     Document Quality 
All would agree that Paul Aitken provided very careful and complete 
reviews throughout the development process; he left no stone unturned.

Personnel 
Al Morton  is shepherd.




From acmorton@att.com  Mon Apr 23 14:44:40 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 7D49621E800F for <bmwg@ietfa.amsl.com>; Mon, 23 Apr 2012 14:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.578
X-Spam-Level: 
X-Spam-Status: No, score=-105.578 tagged_above=-999 required=5 tests=[AWL=0.218, 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 mRKctevqOE0H for <bmwg@ietfa.amsl.com>; Mon, 23 Apr 2012 14:44:40 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id DE7C011E8072 for <bmwg@ietf.org>; Mon, 23 Apr 2012 14:44:39 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 74dc59f4.0.483416.00-424.1339206.nbfkord-smmo06.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 23 Apr 2012 21:44:39 +0000 (UTC)
X-MXL-Hash: 4f95cd4762fc51bf-29de34eebba60a9409d847c68462ea38265eaa03
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 q3NLiclN021202 for <bmwg@ietf.org>; Mon, 23 Apr 2012 17:44:39 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q3NLiWoi021150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Mon, 23 Apr 2012 17:44:32 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Mon, 23 Apr 2012 17:44:23 -0400
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 q3NLiMZo016753 for <bmwg@ietf.org>; Mon, 23 Apr 2012 17:44:22 -0400
Received: from mailgw1.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 q3NLiJN5016688 for <bmwg@ietf.org>; Mon, 23 Apr 2012 17:44:19 -0400
Message-Id: <201204232144.q3NLiJN5016688@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-227-140.vpn.east.att.com[135.70.227.140](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120423214109gw1004orvve>; Mon, 23 Apr 2012 21:41:09 +0000
X-Originating-IP: [135.70.227.140]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Apr 2012 17:45:30 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
In-Reply-To: <20120423211107.7675.47479.idtracker@ietfa.amsl.com>
References: <20120423211107.7675.47479.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
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=1ddunAWZQ7IA:10 a=lMCxKS9xwtsA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=dhjbXmRlediJY0mM9JgA:9 a=CjuIK1q_8ugA:10]
Subject: Re: [bmwg] Document Action: 'IP Flow Information Accounting and Export	Benchmarking Methodology' to Informational RFC	(draft-ietf-bmwg-ipflow-meth-10.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, 23 Apr 2012 21:44:40 -0000

At 05:11 PM 4/23/2012, The IESG wrote:
>The IESG has approved the following document:
>- 'IP Flow Information Accounting and Export Benchmarking Methodology'
>   (draft-ietf-bmwg-ipflow-meth-10.txt) as an Informational RFC
>
>This document is the product of the Benchmarking Methodology Working
>Group.

Congratulations to Jan on your first approved draft,
and to all members of the working group who helped,
especially Paul Aitken.

This draft has come a long way since Dublin!
Al
bmwg chair


From internet-drafts@ietf.org  Thu Apr 26 06:59:42 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 B73A221F864F; Thu, 26 Apr 2012 06:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, 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 rEAqLyLJdUjJ; Thu, 26 Apr 2012 06:59:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F309E21F8425; Thu, 26 Apr 2012 06:59:41 -0700 (PDT)
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: 4.01p1
Message-ID: <20120426135941.11108.84298.idtracker@ietfa.amsl.com>
Date: Thu, 26 Apr 2012 06:59:41 -0700
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-2544-as-03.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: Thu, 26 Apr 2012 13:59:42 -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           : RFC 2544 Applicability Statement: Use on Production Netw=
orks Considered Harmful
	Author(s)       : Scott Bradner
                          Kevin Dubray
                          Jim McQuaid
                          Al Morton
	Filename        : draft-ietf-bmwg-2544-as-03.txt
	Pages           : 9
	Date            : 2012-04-26

   Benchmarking Methodology Working Group (BMWG) has been developing key
   performance metrics and laboratory test methods since 1990, and
   continues this work at present.  Recent application of the methods
   beyond their intended scope is cause for concern.  This memo
   clarifies the scope of RFC 2544 and other benchmarking work for the
   IETF community.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-2544-as-03.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-2544-as-03.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bmwg-2544-as/


From dworley@avaya.com  Fri Apr 27 15:01:29 2012
Return-Path: <dworley@avaya.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 83A4C21F8600; Fri, 27 Apr 2012 15:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.837
X-Spam-Level: 
X-Spam-Status: No, score=-102.837 tagged_above=-999 required=5 tests=[AWL=-0.238, 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 DIdhL54BGIWP; Fri, 27 Apr 2012 15:01:28 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id ECF1621F85FF; Fri, 27 Apr 2012 15:01:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANcVm0/GmAcF/2dsb2JhbABEsgSBB4IQEig4BxIBFRcJCUInBAENDQwOh2sLngidC4sCgmqCTmMElw6FBYoqgwSBOA
X-IronPort-AV: E=Sophos;i="4.75,493,1330923600";  d="scan'208";a="6588193"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 27 Apr 2012 18:01:25 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 27 Apr 2012 17:58:47 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 27 Apr 2012 18:01:25 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "rai@ietf.org" <rai@ietf.org>, Al Morton <acmorton@att.com>, "draft-ietf-bmwg-sip-bench-term@tools.ietf.org" <draft-ietf-bmwg-sip-bench-term@tools.ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Date: Fri, 27 Apr 2012 17:56:42 -0400
Thread-Topic: RAI-ART review of draft-ietf-bmwg-sip-bench-term-04 and draft-ietf-bmwg-sip-bench-meth-04
Thread-Index: AQHNJMFJRhoQSDLmPUGO2SgZHs/AAA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0A88@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Sat, 28 Apr 2012 12:09:25 -0700
Cc: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: [bmwg] RAI-ART review of draft-ietf-bmwg-sip-bench-term-04 and draft-ietf-bmwg-sip-bench-meth-04
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, 27 Apr 2012 22:01:29 -0000

I am the assigned RAI-ART reviewer for this draft.  For background on
RAI-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/rai/trac/wiki/RaiArtfaq>.  Please
resolve these comments along with any other comments you may receive.

This draft is on the right track but has open issues, described in the
review.

Please note that I am quite familiar with SIP but have little
familiarity with benchmarking.  Thus, some of the points I make might
have implicit answers in the usual practice of benchmarking.  But
since one audience of these documents is the SIP community, such
implicit answers should probably be made explicit.

I. Technical issues

A. Media

The drafts seem to be undecided as to whether they want to benchmark
media processing or not.  At one point, it says that the benchmarking
is entirely in the signaling plane.  At another point, it is specified
how to set the number of media streams per INVITE dialog.  I suspect
the conflict is that there are devices the WG wants to benchmark which
do handle the media and their media handling affects performance
significantly, but the WG is unsure how to parametrize media
benchmarking.

The simplest situation, of course, is if the DUT is a proxy and the
media bypasses it entirely.  Beyond that, even in the simplest media
relaying situations, significant processing costs can arise.  Even if
the DUT isn't transcoding, it may have to rewrite the RTP codec
numbers (as it may have modified the SDP passing through it).  In more
complex situations, the DUT may have to transcode the codecs.

Some consideration has to be made of how to specify exactly what the
media loads are.  SDP already has ways to specify the exact encoding
of media streams, including the number of samples per packet, which
implies the packet size and packet rate.  These drafts only allow
specifying the packet size as a benchmark parameter, but packet size
is notoriously ambiguous -- which layers of encapsulation of the
encoded media are counted?  But specifying the detailed encoding
side-steps that question.

The draft wants to consider the duration of a media stream to be
separately adjustable from the duration of the containing dialog, but
the draft explicitly places out of scope the re-INVITE which is
necessary to accomplish that realistically (that is, with the
signaling matching the presented media packets).

B. INVITE dialog structure

The drafts seem to want to consider the establishment (or failure
thereof) of an INVITE dialog to be instantaneous, after which the
dialog continues for a chosen length of time, and then vanishes
instantly.  Little or no consideration is given to the various
scenarios of call establishment, including the most common case:
INVITE sent -- 183 response -- significant delay -- 200 response.
Dialog teardown is not conceptualized as being a processing step that
involves significant cost and may fail:  "Session disconnect is not
considered in the scope of this work item."

This lack of consideration is enhanced in the forking cases, as the
variety of scenarios (and their durations) increases.

In addition, the drafts only consider forking which is done within the
DUT, whereas it will be common in practice for forking to be done
downstream of the DUT, presenting the DUT with a stream of 1xx
responses from multiple endpoints, with a 2xx after an extended delay.

Also, in regard to signaling benchmarking, INVITEs that ultimately
fail are likely to be as costly as INVITEs that succeed, but there
doesn't seem to be a defined parameter "fraction of attempted calls
which succeed" (which controls the callee EAs).

C. Loop detection

All discussions of loop detection needs to based on the revised loop
detection requirements in RFC 5393.

D. Authentication

In some SIP operations, authentication is commonly done.  This can
have various effects on the message flows that need to be taken into
account in the benchmarks.

For instance, a registrar may require that the registering UA
authenticate itself.  Commonly, the UA sends a REGISTER request, which
is rejected with 401 because it contains a nonce that is too old.  The
UA then immediately sends another REGISTER with the nonce provided in
the 401 response, and that request receives a 200 response.

In this scenario, the number of effective REGISTER requests is half of
the total REGISTER requests, leading to an apparent attempt failure
rate of 50%, even though the middlebox is doing the Right Thing 100%
of the time.  This suggests that the definition of "attempt failure"
needs to be updated so that a 4xx response "passed upstream" by the
DUT is not counted as an attempt failure.

In other scenarios, the DUT itself might be expected to enforce SIP
authentication, which would require a somewhat different definition of
attempt failure, and would be expected to have lower throughput.

So some thought needs to be given as to whether these scenarios are
to be benchmarked, and to document how authentication is to be handled
in whatever benchmarks are defined.

II. Editorial issues

The drafts appear to me to be, well, drafts.  That is, they generally
contain the intended technical content but the exposition is not
complete or clear, and at points the reader has to guess at the exact
meaning.  At various points the sentences are not correct English,
references are not complete or correct, and there are various points
of contradiction between different parts of the documents.

The document needs a proper final revision, with each paragraph edited
over carefully to maximize its clarity and to verify that all parts of
the documents are consistent with each other.

Examples of editorial problems are:

draft-ietf-bmwg-sip-bench-term-04

section 1

   The term Throughput is defined in RFC2544 [RFC2544].

The definition is in RFC 1242; RFC 2544 refers to RFC 1242.

   This document uses existing terminology defined in other BMWG work.
   Examples include, but are not limited to:

      Device under test (DUT) (c.f., Section 3.1.1 RFC 2285 [RFC2285]).
      System under test (SUT) (c.f., Section 3.1.2, RFC 2285 [RFC2285]).

In what way would the reader determine the relevant "other BMWG work"?
This reference needs to be made definite in some way.

      The behavior of a stateful proxy is further defined in Section
      16.

This sentence was copied directly from RFC 3261, in whose section 16
the referenced definition exists.  However, *this* document has no
section 16.

section 2.2

The figures are inconsistent in how they label the "Tester" boxes as
"EA" or not.  Is this difference meaningful?

Figures 9 and 10 show "SUT" embracing the entire test setup, including
the "Tester" boxes, whereas RFC 2285 section 3.1.2 says that SUT does
not include the tester components of the setup.

section 3.1.1

The various components of a "session" (usually "dialog" in SIP
terminology) are given quasi-mathematical names that look peculiar to
me.  Worse, they're not completely correct: since each RTP stream has
a corresponding RTCP stream, "session[x].medc" should be
"session[x].medc[y]".  (Is there any benefit of introducing this
symbolism?)

section 3.1.5

This section defines "overload" and then says "The distinction between
an overload condition and other failure scenarios is outside the scope
of this document which is blackbox testing."  If the distinction is
outside the scope, why is there a definition here?

section 3.1.6

The definition of "Session Attempt" seems to be incorrect.  Of course,
a session attempt is each sending of an INVITE/SUBSCRIBE/MESSAGE,
whether or not it is ultimately successful.  But the definition written
makes "session attempt" a time-varying property, which is true only
until a response is received by the EA.

section 3.1.8

      An IS is identified by the Call-ID, To-tag, and From-tag of the
      SIP message that establishes the session.

As written, this is incorrect, as the to-tag is present only in the
response(s) to the INVITE.

      2.  If a media session is described in the SDP body of the
          signaling message, then the media session is established by
          the end of Establishment Threshold Time (c.f.  Section 3.3.3).

This sentence is correct as far as it goes, but there is no clear
description (that I can tell) of when a media session is
"established".  Indeed, it's not clear to me what a proper way to set
up the media is -- in real SIP systems, a proxy or SBC can start
receiving early media from a callee before it has received *any* SIP
responses from the callee, and the middlebox can have some difficulty
matching the RTP to a dialog being set up.  So the exact details of
when to start the media flows are needed to make the benchmarking
process reproducible.

section 3.2.3

This section defines "SIP-Aware Stateful Firewall" as=20

      Device in test topology that provides Denial-of-Service (DoS)
      Protection to the Signaling and Media Planes for the EAs and
      Signaling Server

But a device can be a SIP-Aware Stateful Firewall (in the ordinary
sense of the words) without providing DoS protection.

section 3.3.2

"IS Media Attempt Rate" is defined as

      Configuration on the EA for number of ISs with Associated Media to
      be established at the DUT per continuous one- second time
      intervals.

However, "established" should be "attempted".

section 3.3.3

      Configuration of the EA for representing the amount of time that
      an EA will wait before declaring a Session Attempt Failure.

The discussion makes clear that there may be different Establishment
Threshold Times for IS and NS, but these times are written about in
most places as if they were the same.

draft-ietf-bmwg-sip-bench-meth-04

section 2

Refers to "Presence Rate", but draft-ietf-bmwg-sip-bench-term-04 says
that presence is out of scope.

section 4

What is the relationship between the data items described in this
draft's "Benchmarking Considerations" and
draft-ietf-bmwg-sip-bench-term-04's "Test Setup Parameters"?

section 4.2

I'm having trouble understanding the various terms that include the
word "server", including "Signaling Server", "The Server", "SIP
Server".  Are these intended to have the same meaning?  Are they
intended to cover the whole range of SIP "middleboxes" (including,
e.g., proxies)?  In section 2 is

   The DUT is a SIP Server, which
   may be any [RFC3261] conforming device.  The SUT can be any device or
   group of devices containing RFC 3261 conforming functionality along
   with Firewall and/or NAT functionality.

If read literally, that would *exclude* pure proxies, since they don't
have firewall or NAT functionality.

section 4.3

References "Figures 4 and 5", which don't exist.  Does it mean to
reference draft-ietf-bmwg-sip-bench-term-04?

section 4.9

The formatting of the pseudocode is inconsistent.  The variable "c"
should be boolean rather than 0/1.

section 6.6

      1.  If the DUT is being benchmarked as a proxy or B2BUA, and
          forking is supported in the DUT, then configure the DUT in the
          test topology shown in Figure 5 in [I-D.sip-bench-term].  If
          the DUT does not support forking, then this step can be
          skipped.
      2.  Configure a SUT according to the test topology shown in Figure
          8 of [I-D.sip-bench-term].

It's not clear to me how one can configure the DUT/SUT according to
both figures 5 and 8.  And neither figure shows two callee EAs.

The text suggests that DUTs that do not support forking can be tested,
even though this is a test specifically of performance when the DUT is
doing forking.

Dale
