
From mhamilton@breakingpoint.com  Wed Oct  3 13:38:17 2012
Return-Path: <mhamilton@breakingpoint.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 AC3AE21F8682 for <bmwg@ietfa.amsl.com>; Wed,  3 Oct 2012 13:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlejiqkCVFll for <bmwg@ietfa.amsl.com>; Wed,  3 Oct 2012 13:38:17 -0700 (PDT)
Received: from mail.breakingpoint.com (mail.breakingpoint.com [65.36.7.12]) by ietfa.amsl.com (Postfix) with ESMTP id 1D52221F8680 for <bmwg@ietf.org>; Wed,  3 Oct 2012 13:38:17 -0700 (PDT)
Received: from EXCHANGE.securitytestsystems.com ([::1]) by EXCHANGE.securitytestsystems.com ([::1]) with mapi id 14.01.0355.002; Wed, 3 Oct 2012 15:38:10 -0500
From: Mike Hamilton <mhamilton@breakingpoint.com>
To: Al Morton <acmorton@att.com>, "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: [bmwg] Adoption of Router/Basic BGP Convergence Drafts
Thread-Index: AQHNVUJE0Nkg+i68CUulzTJwWBSjNJePj1gAgBkUIIA=
Date: Wed, 3 Oct 2012 20:38:09 +0000
Message-ID: <CC920C43.1D669%mhamilton@breakingpoint.com>
In-Reply-To: <201209171641.q8HGf4I2015034@alpd052.aldc.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.10.15.243]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <46AC9F576E01F14CAAF25772ED5F8739@breakingpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [bmwg] Adoption of Router/Basic BGP Convergence Drafts
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, 03 Oct 2012 20:38:17 -0000

I support adoption of this item.

Thanks,
Mike


-----Original Message-----
From: Al Morton <acmorton@att.com>
Date: Monday, September 17, 2012 11:39 AM
To: "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [bmwg] Adoption of Router/Basic BGP Convergence Drafts

>BMWG,
>
>I am now re-asking the adoption question for:
>
>>Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence
>>http://tools.ietf.org/html/draft-papneja-bgp-basic-dp-convergence-03
>
>as planned at IETF-84.
>
>Please review and respond to the list by Oct 8, according to the original
>request below.  Don't let the Sept 27 expiration date bother you.
>
>regards,
>Al
>bmwg chair
>
>
>At 11:25 AM 6/28/2012, Al Morton wrote:
>>BMWG,
>>
>>We (still) have a charter item on BGP Convergence:
>>Basic BGP Convergence Benchmarking Methodology to IESG Review (overdue)
>>
>>Over the last year or so, we've discussed two drafts that
>>will help to satisfy the milestone.  We've also seen some results of
>>implementation and testing at our last face2face session.
>>
>>The two drafts are:
>>
>>Convergence benchmarking on contemporary routers
>>http://tools.ietf.org/id/draft-varlashkin-router-conv-bench-00.txt
>>
>>Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence
>>http://tools.ietf.org/html/draft-papneja-bgp-basic-dp-convergence-03
>>
>>
>>The combination of these drafts address both the milestone and
>>issues with non-convergence path restoration that has come-up
>>in IESG comments in the past.
>>
>>Therefore, I now ask whether the working group members feel we
>>should adopt these as WG drafts. So:
>>
>>1. Please Read the Drafts by July 19th, 2012.
>>
>>2. Respond with your review, and
>>
>>3. give your impressions on whether they are sufficiently clear in their
>>approach and direction, such that we can complete them in a timely
>>fashion in the working group.
>>
>>That's it!
>>
>>regards,
>>Al
>>bmwg chair
>>
>>_______________________________________________
>>bmwg mailing list
>>bmwg@ietf.orghttps://www.ietf.org/mailman/listinfo/bmwg
>
>_______________________________________________
>bmwg mailing list
>bmwg@ietf.org
>https://www.ietf.org/mailman/listinfo/bmwg


From acmorton@att.com  Sun Oct  7 18:23:48 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 BC05D21F8713 for <bmwg@ietfa.amsl.com>; Sun,  7 Oct 2012 18:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.74
X-Spam-Level: 
X-Spam-Status: No, score=-104.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kBEo8OugxIF for <bmwg@ietfa.amsl.com>; Sun,  7 Oct 2012 18:23:47 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 7C20C21F86C2 for <bmwg@ietf.org>; Sun,  7 Oct 2012 18:23:47 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 22b22705.0.130928.00-467.355802.nbfkord-smmo07.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 08 Oct 2012 01:23:47 +0000 (UTC)
X-MXL-Hash: 50722b2355977f42-74107e827a493312ca34211e0510ecd92600355f
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q981NkkP026544 for <bmwg@ietf.org>; Sun, 7 Oct 2012 18:23:46 -0700
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q981NeXa026532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Sun, 7 Oct 2012 18:23:40 -0700
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint04.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Sun, 7 Oct 2012 18:23:31 -0700
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 q981NSx6030811 for <bmwg@ietf.org>; Sun, 7 Oct 2012 21:23:29 -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 q981NK1Z030644 for <bmwg@ietf.org>; Sun, 7 Oct 2012 21:23:23 -0400
Received: from lt-hp1044652.att.com (vpn-130-10-228-200.vpn.sest.att.com[130.10.228.200](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20121008012222gw100sspeje>; Mon, 8 Oct 2012 01:22:24 +0000
X-Originating-IP: [130.10.228.200]
Message-Id: <7.0.1.0.0.20121007155337.0745c910@att.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sun, 07 Oct 2012 21:22:48 -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-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=2.0 cv=A6nbydqG c=1 sm=0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a]
X-AnalysisOut: [=Ae4mP6Td2dcA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=kj9]
X-AnalysisOut: [zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=JRt0dW6st3YA:10 a=48vgC7mU]
X-AnalysisOut: [AAAA:8 a=mjsnpKjGOMyym_eeNEsA:9 a=CjuIK1q_8ugA:10 a=AM14pv]
X-AnalysisOut: [5mMGwA:10]
Subject: [bmwg] Brief WG Status
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, 08 Oct 2012 01:23:48 -0000

BMWG,

A brief status and reminder of action item assignments,
follows:

We have the
Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence
http://tools.ietf.org/html/draft-papneja-bgp-basic-dp-convergence-03
on the table for adoption. So far, support has been a little light,
but there's still some time to read and reply...

We are expecting revised drafts for SIP device benchmarking,
please make some time to read these before we meet in Atlanta.

Various folks volunteered to read some outstanding drafts when
we met last.

Bill Cerveny and Benoit Claise volunteered to read the
Power Benchmarking Draft
http://tools.ietf.org/html/draft-manral-bmwg-power-usage-02

Also, Mike Hamilton volunteered to read the Data Center Bridge draft:
http://tools.ietf.org/html/draft-player-dcb-benchmarking-04

We need to find additional reviewers before we adopt either of
these drafts.

In other work, we have been attempting to move the RFC 2544 AS draft
through the IESG for >4months now. What was a straightforward development
to achieve consensus in the BMWG has seen unexpected resistance from
one IESG member. Fortunately, there are IETF processes designed to
deal with exactly this situation, and we will pursue that course if
necessary. This activity has taken-up more of my "IETF" time than
it should have, and it's an area where we need progress so that other
topics can get attention. There have been 3 revisions since IETF Last Call,
and there is likely to be one more. However, the central message of
the draft as embodied in the title has not changed.

Last but not least, we have a session scheduled on the IETF-85 agenda,
and so it's time for authors and other participants to consider how
we can best use our face2face meeting time.

regards,
Al
bmwg chair


From fcalabri@cisco.com  Thu Oct 11 08:18:49 2012
Return-Path: <fcalabri@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 5C70611E80E1 for <bmwg@ietfa.amsl.com>; Thu, 11 Oct 2012 08:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9obbuGwXPQq for <bmwg@ietfa.amsl.com>; Thu, 11 Oct 2012 08:18:48 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 5429411E80DE for <bmwg@ietf.org>; Thu, 11 Oct 2012 08:18:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7405; q=dns/txt; s=iport; t=1349968722; x=1351178322; h=from:to:subject:date:message-id:mime-version; bh=Ly48dqbOc80jluBj8IA+VeNbU/d7WEu8spqawGKZYvs=; b=lOYvWpK6hA8Dq0H16WSHTbV7hE0gez3axM585dHsg60yxxEqr8jVPM0P xUBQn7rpf57KXyuUswabTQ5kBCW0tkkL91koiKzdNFyCzJaOplnb8ZszC RA3NNkQNRHkS5HDzfKaWriAyP0hVVKVy2BMr37YEumP0Jhzvj8BN6+wJT I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFABfidlCtJXHB/2dsb2JhbABEgku8eoEIghkHAQEBBAEBAQ8BWxcGAQgRAwECAQodLgsUCQoEEwgBGYUnB4I0C5hSgSigIItHhUBgA5cCjTCBa4Jtghc
X-IronPort-AV: E=Sophos;i="4.80,572,1344211200";  d="scan'208,217";a="130606654"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-5.cisco.com with ESMTP; 11 Oct 2012 15:18:41 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q9BFIftS007381 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <bmwg@ietf.org>; Thu, 11 Oct 2012 15:18:41 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.204]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.001; Thu, 11 Oct 2012 10:18:41 -0500
From: "Fernando Calabria (fcalabri)" <fcalabri@cisco.com>
To: "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: [bmwg] Adoption of Router/Basic BGP Convergence Drafts
Thread-Index: AQHNp8OxE2kfIxsGvUuNXobIIscrHA==
Date: Thu, 11 Oct 2012 15:18:40 +0000
Message-ID: <0C48A5C715C20C4D8F94B6E3268CB21B0E39F9@xmb-aln-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [64.102.130.163]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19262.000
x-tm-as-result: No--35.505800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_0C48A5C715C20C4D8F94B6E3268CB21B0E39F9xmbalnx03ciscocom_"
MIME-Version: 1.0
Subject: Re: [bmwg] Adoption of Router/Basic BGP Convergence Drafts
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, 11 Oct 2012 15:18:49 -0000

--_000_0C48A5C715C20C4D8F94B6E3268CB21B0E39F9xmbalnx03ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Apologies for my late reply=85

The comments I had back in Prague were   already addressed in the current r=
evision ,  I have no further comments so +1 for the adoption of the documen=
t =85

Rgds


Fernando


-------- Original Message --------
Subject:        Re: [bmwg] Adoption of Router/Basic BGP Convergence Drafts
Date:   Mon, 17 Sep 2012 12:39:36 -0400
From:   Al Morton <acmorton@att.com><mailto:acmorton@att.com>
To:     <bmwg@ietf.org><mailto:bmwg@ietf.org>



BMWG,

I am now re-asking the adoption question for:

>Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence
>http://tools.ietf.org/html/draft-papneja-bgp-basic-dp-convergence-03

as planned at IETF-84.

Please review and respond to the list by Oct 8, according to the original
request below.  Don't let the Sept 27 expiration date bother you.

regards,
Al
bmwg chair


At 11:25 AM 6/28/2012, Al Morton wrote:
>BMWG,
>
>We (still) have a charter item on BGP Convergence:
>Basic BGP Convergence Benchmarking Methodology to IESG Review (overdue)>
>Over the last year or so, we've discussed two drafts that
>will help to satisfy the milestone.  We've also seen some results of
>implementation and testing at our last face2face session.
>
>The two drafts are:
>
>Convergence benchmarking on contemporary routers
>http://tools.ietf.org/id/draft-varlashkin-router-conv-bench-00.txt
>
>Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence
>http://tools.ietf.org/html/draft-papneja-bgp-basic-dp-convergence-03
>
>
>The combination of these drafts address both the milestone and
>issues with non-convergence path restoration that has come-up
>in IESG comments in the past.
>
>Therefore, I now ask whether the working group members feel we
>should adopt these as WG drafts. So:
>
>1. Please Read the Drafts by July 19th, 2012.
>
>2. Respond with your review, and
>
>3. give your impressions on whether they are sufficiently clear in their
>approach and direction, such that we can complete them in a timely
>fashion in the working group.
>
>That's it!
>
>regards,
>Al
>bmwg chair
>
>_______________________________________________
>bmwg mailing list
>bmwg@ietf.orghttps://www.ietf.org/mailman/listinfo/bmwg<mailto:bmwg@ietf.o=
rghttps://www.ietf.org/mailman/listinfo/bmwg>

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





--_000_0C48A5C715C20C4D8F94B6E3268CB21B0E39F9xmbalnx03ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <D8589B6ED9D5014B9B333B6E1251447B@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Apologies for my late reply=85</div>
<div><br>
</div>
<div>The comments I had back in Prague were &nbsp; already addressed in the=
 current revision , &nbsp;I have no further comments so &#43;1 for the adop=
tion of the document =85</div>
<div><br>
</div>
<div>Rgds&nbsp;</div>
<div><br>
</div>
<div><br>
</div>
<div>Fernando&nbsp;</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div class=3D"moz-forward-container" style=3D"font-family: Calibri; font-si=
ze: medium; ">
-------- Original Message --------
<table class=3D"moz-email-headers-table" border=3D"0" cellpadding=3D"0" cel=
lspacing=3D"0">
<tbody>
<tr>
<th align=3D"RIGHT" nowrap=3D"nowrap" valign=3D"BASELINE">Subject:</th>
<td>Re: [bmwg] Adoption of Router/Basic BGP Convergence Drafts</td>
</tr>
<tr>
<th align=3D"RIGHT" nowrap=3D"nowrap" valign=3D"BASELINE">Date:</th>
<td>Mon, 17 Sep 2012 12:39:36 -0400</td>
</tr>
<tr>
<th align=3D"RIGHT" nowrap=3D"nowrap" valign=3D"BASELINE">From:</th>
<td>Al Morton&nbsp;<a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:acmort=
on@att.com">&lt;acmorton@att.com&gt;</a></td>
</tr>
<tr>
<th align=3D"RIGHT" nowrap=3D"nowrap" valign=3D"BASELINE">To:</th>
<td><a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:bmwg@ietf.org">&lt;bm=
wg@ietf.org&gt;</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>BMWG,

I am now re-asking the adoption question for:

&gt;Basic BGP Convergence Benchmarking Methodology for Data Plane Convergen=
ce
&gt;<a class=3D"moz-txt-link-freetext" href=3D"http://tools.ietf.org/html/d=
raft-papneja-bgp-basic-dp-convergence-03">http://tools.ietf.org/html/draft-=
papneja-bgp-basic-dp-convergence-03</a>

as planned at IETF-84.

Please review and respond to the list by Oct 8, according to the original
request below.  Don't let the Sept 27 expiration date bother you.

regards,
Al
bmwg chair


At 11:25 AM 6/28/2012, Al Morton wrote:
&gt;BMWG,
&gt;
&gt;We (still) have a charter item on BGP Convergence:
&gt;Basic BGP Convergence Benchmarking Methodology to IESG Review (overdue)=
&gt;
&gt;Over the last year or so, we've discussed two drafts that
&gt;will help to satisfy the milestone.  We've also seen some results of
&gt;implementation and testing at our last face2face session.
&gt;
&gt;The two drafts are:
&gt;
&gt;Convergence benchmarking on contemporary routers
&gt;<a class=3D"moz-txt-link-freetext" href=3D"http://tools.ietf.org/id/dra=
ft-varlashkin-router-conv-bench-00.txt">http://tools.ietf.org/id/draft-varl=
ashkin-router-conv-bench-00.txt</a>
&gt;
&gt;Basic BGP Convergence Benchmarking Methodology for Data Plane Convergen=
ce
&gt;<a class=3D"moz-txt-link-freetext" href=3D"http://tools.ietf.org/html/d=
raft-papneja-bgp-basic-dp-convergence-03">http://tools.ietf.org/html/draft-=
papneja-bgp-basic-dp-convergence-03</a>
&gt;
&gt;
&gt;The combination of these drafts address both the milestone and
&gt;issues with non-convergence path restoration that has come-up
&gt;in IESG comments in the past.
&gt;
&gt;Therefore, I now ask whether the working group members feel we
&gt;should adopt these as WG drafts. So:
&gt;
&gt;1. Please Read the Drafts by July 19th, 2012.
&gt;
&gt;2. Respond with your review, and
&gt;
&gt;3. give your impressions on whether they are sufficiently clear in thei=
r
&gt;approach and direction, such that we can complete them in a timely
&gt;fashion in the working group.
&gt;
&gt;That's it!
&gt;
&gt;regards,
&gt;Al
&gt;bmwg chair
&gt;
&gt;_______________________________________________
&gt;bmwg mailing list
&gt;<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:bmwg@ietf.orghttps=
://www.ietf.org/mailman/listinfo/bmwg">bmwg@ietf.orghttps://www.ietf.org/ma=
ilman/listinfo/bmwg</a>

_______________________________________________
bmwg mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:bmwg@ietf.org">bmwg@ie=
tf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/bmwg">https://www.ietf.org/mailman/listinfo/bmwg</a>

</pre>
<br>
</div>
</div>
<br>
</div>
</body>
</html>

--_000_0C48A5C715C20C4D8F94B6E3268CB21B0E39F9xmbalnx03ciscocom_--

From internet-drafts@ietf.org  Mon Oct 22 12:27:16 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 AC04C21F876B; Mon, 22 Oct 2012 12:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V7QiQrUp4gjZ; Mon, 22 Oct 2012 12:27:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92A5C21F8769; Mon, 22 Oct 2012 12:27:13 -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.34
Message-ID: <20121022192713.3548.22751.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 12:27:13 -0700
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-2544-as-08.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, 22 Oct 2012 19:27:16 -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 Group 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-08.txt
	Pages           : 11
	Date            : 2012-10-22

Abstract:
   Benchmarking Methodology Working Group (BMWG) has been developing key
   performance metrics and laboratory test methods since 1990, and
   continues this work at present.  The methods described in RFC 2544
   are intended to generate traffic that overloads network device
   resources in order to assess their capacity.  Overload of shared
   resources would likely be harmful to user traffic performance on a
   production network, and there are further negative consequences
   identified with production application of the methods.  This memo
   clarifies the scope of RFC 2544 and other IETF BMWG benchmarking work
   for isolated test environments only, and encourages new standards
   activity for measurement methods applicable outside that scope.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bmwg-2544-as-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bmwg-2544-as-08


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


From internet-drafts@ietf.org  Mon Oct 22 13:29:18 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 DFA2221F8451; Mon, 22 Oct 2012 13:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L5EHqCs1UsOH; Mon, 22 Oct 2012 13:29:18 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 771D721F8434; Mon, 22 Oct 2012 13:29:18 -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.34
Message-ID: <20121022202918.15576.93474.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 13:29:18 -0700
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-sip-bench-meth-05.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, 22 Oct 2012 20:29:19 -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 Group of=
 the IETF.

	Title           : Methodology for Benchmarking SIP Networking Devices
	Author(s)       : Carol Davids
                          Vijay K. Gurbani
                          Scott Poretsky
	Filename        : draft-ietf-bmwg-sip-bench-meth-05.txt
	Pages           : 20
	Date            : 2012-10-22

Abstract:
   This document describes the methodology for benchmarking Session
   Initiation Protocol (SIP) performance as described in SIP
   benchmarking terminology document.  The methodology and terminology
   are to be used for benchmarking signaling plane performance with
   varying signaling and media load.  Both scale and establishment rate
   are measured by signaling plane performance.  The SIP Devices to be
   benchmarked may be a single device under test (DUT) or a system under
   test (SUT).  Benchmarks can be obtained and compared for different
   types of devices such as SIP Proxy Server, SBC, and server paired
   with a media relay or Firewall/NAT device.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-meth

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bmwg-sip-bench-meth-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bmwg-sip-bench-meth-05


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


From internet-drafts@ietf.org  Tue Oct 23 09:16:18 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 1F79511E8107; Tue, 23 Oct 2012 09:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkb-cUMnYj0E; Tue, 23 Oct 2012 09:16:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F0D311E80E4; Tue, 23 Oct 2012 09:16:17 -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.34
Message-ID: <20121023161617.11689.53368.idtracker@ietfa.amsl.com>
Date: Tue, 23 Oct 2012 09:16:17 -0700
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-sip-bench-term-05.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, 23 Oct 2012 16:16:18 -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 Group of=
 the IETF.

	Title           : Terminology for Benchmarking Session Initiation Protocol=
 (SIP) Networking Devices
	Author(s)       : Carol Davids
                          Vijay K. Gurbani
                          Scott Poretsky
	Filename        : draft-ietf-bmwg-sip-bench-term-05.txt
	Pages           : 38
	Date            : 2012-10-22

Abstract:
   This document provides a terminology for benchmarking the SIP
   performance of networking devices.  The term performance in this
   context means the capacity of the device- or system-under-test to
   process SIP messages.  Terms are included for test components, test
   setup parameters, and performance benchmark metrics for black-box
   benchmarking of SIP networking devices.  The performance benchmark
   metrics are obtained for the SIP signaling plane only.  The terms are
   intended for use in a companion methodology document for
   characterizing the performance of a SIP networking device under a
   variety of conditions.  The intent of the two documents is to enable
   a comparison of the capacity of SIP networking devices.  Test setup
   parameters and a methodology document are necessary because SIP
   allows a wide range of configuration and operational conditions that
   can influence performance benchmark measurements.  A standard
   terminology and methodology will ensure that benchmarks have
   consistent definition and were obtained following the same
   procedures.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bmwg-sip-bench-term-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bmwg-sip-bench-term-05


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


From iesg-secretary@ietf.org  Tue Oct 23 12:16:52 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 1A27A11E80EA; Tue, 23 Oct 2012 12:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHXD0zEFceap; Tue, 23 Oct 2012 12:16:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF6F11E80F3; Tue, 23 Oct 2012 12:16:51 -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.34
Message-ID: <20121023191651.15517.83188.idtracker@ietfa.amsl.com>
Date: Tue, 23 Oct 2012 12:16:51 -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: 'RFC 2544 Applicability Statement: Use on Production	Networks Considered Harmful' to Informational RFC	(draft-ietf-bmwg-2544-as-08.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, 23 Oct 2012 19:16:52 -0000

The IESG has approved the following document:
- 'RFC 2544 Applicability Statement: Use on Production Networks
   Considered Harmful'
  (draft-ietf-bmwg-2544-as-08.txt) as 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-2544-as/




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. 

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>

From bmwg@wjcerveny.com  Wed Oct 24 16:01:12 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 1AEA221F8C65 for <bmwg@ietfa.amsl.com>; Wed, 24 Oct 2012 16:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSFOW2izaf9S for <bmwg@ietfa.amsl.com>; Wed, 24 Oct 2012 16:01:11 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 4E02D21F8C11 for <bmwg@ietf.org>; Wed, 24 Oct 2012 16:01:11 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6BE23205D6; Wed, 24 Oct 2012 19:01:10 -0400 (EDT)
Received: from web5.nyi.mail.srv.osa ([10.202.2.215]) by compute6.internal (MEProxy); Wed, 24 Oct 2012 19:01:10 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=ZQbLVcTG5JpD1JHmEZvymYv3sr0=; b=r+cWz 0khJiTlyg93tf7Cm1YcadXEy1XVCTVF92umyhXGeTXUJzkxS8UqKd515fvFuspmH 22nqMEg7RNIrShBbnm904cGZIOTYEUym+ObPQp6YkLoLRF0Io/jGH6zPlY4gZA3Z aSmGaf0lZCpBXfZJtOLa3QDJ+ljSY2nSVDXO3Q=
Received: by web5.nyi.mail.srv.osa (Postfix, from userid 99) id 354714C0123; Wed, 24 Oct 2012 19:01:10 -0400 (EDT)
Message-Id: <1351119670.28914.140661145059693.6BAD76C1@webmail.messagingengine.com>
X-Sasl-Enc: OYCWI3GGrqBxzNvl+49Ahe3aENOl1sSxSC05vy+nwXkO 1351119670
From: Bill Cerveny <bmwg@wjcerveny.com>
To: Al Morton <acmorton@att.com>, bmwg@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface
Date: Wed, 24 Oct 2012 19:01:10 -0400
In-Reply-To: <7.0.1.0.0.20121007155337.0745c910@att.com>
References: <7.0.1.0.0.20121007155337.0745c910@att.com>
Subject: [bmwg] Initial comments on "draft-manral-bmwg-power-usage-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: Wed, 24 Oct 2012 23:01:12 -0000

Below are my initial impressions regarding
"draft-manral-bmwg-power-usage-02", as requested at the last meeting. I
focused primarily on I-D design and content; I did not focus/comment on
grammatical/typographical issues. 

There is a lot of interesting content that could be referenced by
someone wishing to do power measurements on network devices. There is a
lot of background on challenges and factors which can impact power
measurement.

Although the introduction said there would be procedures and metrics
presented in the document, I didn't see what I would consider procedures
in the document. I expected to see something that resembled a discussion
of test setup, objectives and perhaps steps for performing measurements.

>From a strict document design perspective, some of the text in the
introduction probably doesn't belong in the introduction, although it is
interesting and useful material. In particular, the paragraph beginning
"The first step to obtain a network wide view is ..." probably does not
need to be in the introduction, although it does appear the paragraph
could be part of a procedure further in the document.

As you update the document, consider splitting the paragraph "Various
techniques have been defined ...", such that there is a new paragraph
that begins with the sentence "This document defines the ...". The
sentence "This document defines the ..." seems key to describing the
document and I discourage "hiding" it in the middle of a paragraph.

Section 6, "benchmark details", seems a bit shorter than I would have
expected for a benchmarking document. 

In conclusion, I think that the draft is interesting and has potential.
The most important thing is that the draft needs to have procedures
added or the introduction should not state that there are procedures in
the document.  

Regards,

Bill Cerveny

From acmorton@att.com  Thu Oct 25 10:00:58 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 D2AC121F8782 for <bmwg@ietfa.amsl.com>; Thu, 25 Oct 2012 10:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.051
X-Spam-Level: 
X-Spam-Status: No, score=-106.051 tagged_above=-999 required=5 tests=[AWL=0.548, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pw7LDlQpRfX for <bmwg@ietfa.amsl.com>; Thu, 25 Oct 2012 10:00:57 -0700 (PDT)
Received: from nbfkord-smmo08.seg.att.com (nbfkord-smmo08.seg.att.com [209.65.160.95]) by ietfa.amsl.com (Postfix) with ESMTP id C122021F851E for <bmwg@ietf.org>; Thu, 25 Oct 2012 10:00:56 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo08.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 84079805.0.701372.00-468.1909440.nbfkord-smmo08.seg.att.com (envelope-from <acmorton@att.com>);  Thu, 25 Oct 2012 17:00:56 +0000 (UTC)
X-MXL-Hash: 5089704800c02623-dcb0064ddca6600b4bd3ce4a3eda95badb5fbb05
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 q9PH0tvf009527 for <bmwg@ietf.org>; Thu, 25 Oct 2012 13:00:56 -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 q9PH0pHF009496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Thu, 25 Oct 2012 13:00:52 -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>; Thu, 25 Oct 2012 13:00:38 -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 q9PH0cBj028577 for <bmwg@ietf.org>; Thu, 25 Oct 2012 13:00:38 -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 q9PH0WFc028213 for <bmwg@ietf.org>; Thu, 25 Oct 2012 13:00:32 -0400
Received: from lt-hp1044652.att.com (vpn-135-70-189-77.vpn.mwst.att.com[135.70.189.77](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20121025165921gw100r2cf4e>; Thu, 25 Oct 2012 16:59:21 +0000
X-Originating-IP: [135.70.189.77]
Message-Id: <7.0.1.0.0.20121025125637.082f6160@att.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 25 Oct 2012 12:59:20 -0400
To: bmwg@ietf.org, Bill Cerveny <bill@wjcerveny.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <20121023191651.15517.83188.idtracker@ietfa.amsl.com>
References: <20121023191651.15517.83188.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-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=2.0 cv=fKeOK+me c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=fZ0pT5-qH6gA:10 a=x0_q90lkCsMA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=eopgiNfT]
X-AnalysisOut: [iB0A:10 a=48vgC7mUAAAA:8 a=RttCodISAAAA:8 a=OUXY8nFuAAAA:8]
X-AnalysisOut: [ a=avux1bzOcbHoskAZs0UA:9 a=CjuIK1q_8ugA:10 a=70Rp5QzCwSkA]
X-AnalysisOut: [:10 a=peF9eE_zjQwA:10 a=lZB815dzVvQA:10]
Subject: Re: [bmwg] Document Action: 'RFC 2544 Applicability Statement: Use on Production	Networks Considered Harmful' to Informational RFC	(draft-ietf-bmwg-2544-as-08.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, 25 Oct 2012 17:00:58 -0000

I will take this opportunity to publicly thank Bill Cerveny
for serving as Document Shepherd for this Internet-Draft.

Bill, your duties are well and fully complete!
Thank you,
Al
bmwg chair


At 03:16 PM 10/23/2012, The IESG wrote:
>The IESG has approved the following document:
>- 'RFC 2544 Applicability Statement: Use on Production Networks
>    Considered Harmful'
>   (draft-ietf-bmwg-2544-as-08.txt) as 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-2544-as/
>
>
>
>
>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.
>
>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>
>_______________________________________________
>bmwg mailing list
>bmwg@ietf.org
>https://www.ietf.org/mailman/listinfo/bmwg


From vishwas.ietf@gmail.com  Fri Oct 26 15:59:34 2012
Return-Path: <vishwas.ietf@gmail.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 1751321F84C6 for <bmwg@ietfa.amsl.com>; Fri, 26 Oct 2012 15:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ZhUeh6w0Urm for <bmwg@ietfa.amsl.com>; Fri, 26 Oct 2012 15:59:33 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE77F21F84B1 for <bmwg@ietf.org>; Fri, 26 Oct 2012 15:59:32 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so2211360lbo.31 for <bmwg@ietf.org>; Fri, 26 Oct 2012 15:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d8SUyG2mwYmKsOwc9WzEqJ5QH7Cyqt6t5RfaWsC1/WY=; b=l4D1rVe1+agjFwnzATzotsZvulognKTpYAVVms+6HYnAekGIZQIUlu8bVfDn7BZ/wo TOM30+mLNiGPvy+Dxwf3qDhzzAKo/+qMbGTl0a15JaszobBrM9O6jGFNhTA64cKdMnq7 JiMz65LJpjSJXfB+t9bBWcxj+hCHVIk6h1jo5mxZoXnsEUxFm9hau2OGw3Z7S2upAh7u F63NXqTpcOmRTAcpNHTiO7H38NZoFHIFeiz19bqDKx8kBGCYsGbxGCkRkiYeNYWk/bJ6 mSi+WxOwvISCU+kJLzv2d329satVp4py7Xl/jWZNRiNwz6RRgBEhclvKIGwb0zjIi94y i2DA==
MIME-Version: 1.0
Received: by 10.152.47.148 with SMTP id d20mr21483045lan.42.1351292371435; Fri, 26 Oct 2012 15:59:31 -0700 (PDT)
Received: by 10.114.75.110 with HTTP; Fri, 26 Oct 2012 15:59:31 -0700 (PDT)
In-Reply-To: <1351119670.28914.140661145059693.6BAD76C1@webmail.messagingengine.com>
References: <7.0.1.0.0.20121007155337.0745c910@att.com> <1351119670.28914.140661145059693.6BAD76C1@webmail.messagingengine.com>
Date: Fri, 26 Oct 2012 15:59:31 -0700
Message-ID: <CAOyVPHS1kf8fubXX3G=S+SQQom59c8WQDTbOxtt8chPOCFgzEg@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Bill Cerveny <bmwg@wjcerveny.com>
Content-Type: multipart/alternative; boundary=bcaec550ac56c980f604ccfe451b
Cc: Al Morton <acmorton@att.com>, bmwg@ietf.org
Subject: Re: [bmwg] Initial comments on "draft-manral-bmwg-power-usage-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: Fri, 26 Oct 2012 22:59:34 -0000

--bcaec550ac56c980f604ccfe451b
Content-Type: text/plain; charset=ISO-8859-1

Hi Bill,

Thanks a lot for your comments.

The work was started way back around 2007, for a particular Tier-1 ISP who
wanted to reduce their power footprint. We looked at techniques like
Elastic tree, but realized the first thing was to be able to characterize
the power usage on a device.

I will work on your comments and try to update the draft. I did have some
interest from within the EMAN group, but things never materialized in the
past.

Thanks,
Vishwas

On Wed, Oct 24, 2012 at 4:01 PM, Bill Cerveny <bmwg@wjcerveny.com> wrote:

> Below are my initial impressions regarding
> "draft-manral-bmwg-power-usage-02", as requested at the last meeting. I
> focused primarily on I-D design and content; I did not focus/comment on
> grammatical/typographical issues.
>
> There is a lot of interesting content that could be referenced by
> someone wishing to do power measurements on network devices. There is a
> lot of background on challenges and factors which can impact power
> measurement.
>
> Although the introduction said there would be procedures and metrics
> presented in the document, I didn't see what I would consider procedures
> in the document. I expected to see something that resembled a discussion
> of test setup, objectives and perhaps steps for performing measurements.
>
> From a strict document design perspective, some of the text in the
> introduction probably doesn't belong in the introduction, although it is
> interesting and useful material. In particular, the paragraph beginning
> "The first step to obtain a network wide view is ..." probably does not
> need to be in the introduction, although it does appear the paragraph
> could be part of a procedure further in the document.
>
> As you update the document, consider splitting the paragraph "Various
> techniques have been defined ...", such that there is a new paragraph
> that begins with the sentence "This document defines the ...". The
> sentence "This document defines the ..." seems key to describing the
> document and I discourage "hiding" it in the middle of a paragraph.
>
> Section 6, "benchmark details", seems a bit shorter than I would have
> expected for a benchmarking document.
>
> In conclusion, I think that the draft is interesting and has potential.
> The most important thing is that the draft needs to have procedures
> added or the introduction should not state that there are procedures in
> the document.
>
> Regards,
>
> Bill Cerveny
> _______________________________________________
> bmwg mailing list
> bmwg@ietf.org
> https://www.ietf.org/mailman/listinfo/bmwg
>

--bcaec550ac56c980f604ccfe451b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Bill,<br><br>Thanks a lot for your comments.<br><br>The work was started=
 way back around 2007, for a particular Tier-1 ISP who wanted to reduce the=
ir power footprint. We looked at techniques like Elastic tree, but realized=
 the first thing was to be able to characterize the power usage on a device=
.<br>
<br>I will work on your comments and try to update the draft. I did have so=
me interest from within the EMAN group, but things never materialized in th=
e past.<br><br>Thanks,<br>Vishwas<br><br><div class=3D"gmail_quote">On Wed,=
 Oct 24, 2012 at 4:01 PM, Bill Cerveny <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:bmwg@wjcerveny.com" target=3D"_blank">bmwg@wjcerveny.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Below are my initial impressions regarding<b=
r>
&quot;draft-manral-bmwg-power-usage-02&quot;, as requested at the last meet=
ing. I<br>
focused primarily on I-D design and content; I did not focus/comment on<br>
grammatical/typographical issues.<br>
<br>
There is a lot of interesting content that could be referenced by<br>
someone wishing to do power measurements on network devices. There is a<br>
lot of background on challenges and factors which can impact power<br>
measurement.<br>
<br>
Although the introduction said there would be procedures and metrics<br>
presented in the document, I didn&#39;t see what I would consider procedure=
s<br>
in the document. I expected to see something that resembled a discussion<br=
>
of test setup, objectives and perhaps steps for performing measurements.<br=
>
<br>
>From a strict document design perspective, some of the text in the<br>
introduction probably doesn&#39;t belong in the introduction, although it i=
s<br>
interesting and useful material. In particular, the paragraph beginning<br>
&quot;The first step to obtain a network wide view is ...&quot; probably do=
es not<br>
need to be in the introduction, although it does appear the paragraph<br>
could be part of a procedure further in the document.<br>
<br>
As you update the document, consider splitting the paragraph &quot;Various<=
br>
techniques have been defined ...&quot;, such that there is a new paragraph<=
br>
that begins with the sentence &quot;This document defines the ...&quot;. Th=
e<br>
sentence &quot;This document defines the ...&quot; seems key to describing =
the<br>
document and I discourage &quot;hiding&quot; it in the middle of a paragrap=
h.<br>
<br>
Section 6, &quot;benchmark details&quot;, seems a bit shorter than I would =
have<br>
expected for a benchmarking document.<br>
<br>
In conclusion, I think that the draft is interesting and has potential.<br>
The most important thing is that the draft needs to have procedures<br>
added or the introduction should not state that there are procedures in<br>
the document.<br>
<br>
Regards,<br>
<br>
Bill Cerveny<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/bmwg</a><br>
</blockquote></div><br>

--bcaec550ac56c980f604ccfe451b--

From acmorton@att.com  Sat Oct 27 08:55:43 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 BFA9521F8510 for <bmwg@ietfa.amsl.com>; Sat, 27 Oct 2012 08:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.183
X-Spam-Level: 
X-Spam-Status: No, score=-105.183 tagged_above=-999 required=5 tests=[AWL=-0.443, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26wYofmnErFc for <bmwg@ietfa.amsl.com>; Sat, 27 Oct 2012 08:55:43 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA7021F84FB for <bmwg@ietf.org>; Sat, 27 Oct 2012 08:55:38 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 9f30c805.0.2268628.00-201.6270199.nbfkord-smmo07.seg.att.com (envelope-from <acmorton@att.com>);  Sat, 27 Oct 2012 15:55:38 +0000 (UTC)
X-MXL-Hash: 508c03fa73ea8bc7-5ec229e90cf0d2c811a3467792c59c95da8ce6e9
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 q9RFtb2J003895 for <bmwg@ietf.org>; Sat, 27 Oct 2012 11:55:37 -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 q9RFtZFQ003892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Sat, 27 Oct 2012 11:55: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>; Sat, 27 Oct 2012 11:55:17 -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 q9RFtGfX021097 for <bmwg@ietf.org>; Sat, 27 Oct 2012 11:55:16 -0400
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q9RFslFv019840 for <bmwg@ietf.org>; Sat, 27 Oct 2012 11:55:12 -0400
Received: from lt-hp1044652.att.com (vpn-135-70-87-127.vpn.swst.att.com[135.70.87.127](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20121027155335gw100r2chbe>; Sat, 27 Oct 2012 15:53:35 +0000
X-Originating-IP: [135.70.87.127]
Message-Id: <7.0.1.0.0.20121027115121.04b321b8@att.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sat, 27 Oct 2012 11:53:24 -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-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=2.0 cv=YJMoP26x c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=wCj9QHx9Wk0A:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=kj9]
X-AnalysisOut: [zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=6V2q3TDReGMA:10 a=48vgC7mU]
X-AnalysisOut: [AAAA:8 a=wDWduTBN2WS_JirMEJ0A:9 a=CjuIK1q_8ugA:10 a=AM14pv]
X-AnalysisOut: [5mMGwA:10]
Subject: [bmwg] Draft Agenda for IETF-85
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, 27 Oct 2012 15:55:43 -0000

BMWG,

I have uploaded the draft agenda:
http://www.ietf.org/proceedings/85/agenda/agenda-85-bmwg

There are a few items to be resolved, so comments
and feedback welcome on this, as always.

regards from rainy Vienna,
Al

