[bmwg] Status of BMWG Work

Al Morton <acmorton@att.com> Thu, 22 January 2004 19:54 UTC

Received: from optimus.ietf.org ([]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06760 for <bmwg-archive@lists.ietf.org>; Thu, 22 Jan 2004 14:54:34 -0500 (EST)
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ajkts-0004d5-Gq; Thu, 22 Jan 2004 14:54:00 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ajkt2-0004bl-Ii for bmwg@optimus.ietf.org; Thu, 22 Jan 2004 14:53:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06722 for <bmwg@ietf.org>; Thu, 22 Jan 2004 14:53:04 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1Ajksz-00014D-00 for bmwg@ietf.org; Thu, 22 Jan 2004 14:53:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AjksA-0007l3-00 for bmwg@ietf.org; Thu, 22 Jan 2004 14:52:14 -0500
Received: from ckmso1.att.com ([] helo=ckmso1.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1AjkrK-0006Df-00 for bmwg@ietf.org; Thu, 22 Jan 2004 14:51:22 -0500
Received: from attrh5i.attrh.att.com ([]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id i0MJAqiB031225 for <bmwg@ietf.org>; Thu, 22 Jan 2004 14:50:52 -0500
Received: from custsla.mt.att.com ( by attrh5i.attrh.att.com (6.5.032) id 400ABCEB00218BE6; Thu, 22 Jan 2004 14:50:25 -0500
Received: from acmortonw.att.com (acmortonw.mt.att.com []) by custsla.mt.att.com (8.10.2+Sun/8.10.2) with ESMTP id i0MK4AL00276; Thu, 22 Jan 2004 15:04:10 -0500 (EST)
Message-Id: <>
X-Sender: acm@custsla.mt.att.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 22 Jan 2004 14:50:48 -0500
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
Cc: Kevin Dubray <kdubray@juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [bmwg] Status of BMWG Work
Sender: bmwg-admin@ietf.org
Errors-To: bmwg-admin@ietf.org
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>

A brief status of BMWG work follows:

NOTE: your chairmen are diligently working an issue
regarding I-D submissions and missing announcements/postings.
Some of the revised drafts may not yet be available.
If you submit an I-D intended for bmwg, please let us know...

AD/IESG Review
<draft-ietf-bmwg-conterm-05.txt>, revised, under review.
<draft-ietf-bmwg-mcastm-13.txt>, Responding to OPS Directorate Comments
<draft-ietf-bmwg-ospfconv-term-07.txt>,  Revised on OPS Dir Comments
<draft-ietf-bmwg-ospfconv-intraarea-07.txt>, same
<draft-ietf-bmwg-ospfconv-applicability-04.txt>, same

WG Last Call
<draft-ietf-bmwg-fib-meth-01.txt>,  Draft expired. LC on Work ends 2/3.
<draft-ietf-bmwg-dsmterm-08.txt>, Call ended 11/7, w/comment.

<draft-ietf-bmwg-ipsec-term-02.txt>, draft 10/2003, IMIX comments@58
<draft-ietf-bmwg-benchres-term-04.txt>, back in WG, comments@57
<draft-ietf-bmwg-acc-bench-term-01.txt> Revised on comments
<draft-ietf-bmwg-acc-bench-framework-00.txt> New @ IETF 58
<draft-ietf-bmwg-igp-dataplane-conv-term-02.txt> Revised
<draft-ietf-bmwg-igp-dataplane-conv-meth-02.txt> Revised
<draft-ietf-bmwg-igp-dataplane-conv-app-02.txt> Revised

Expired BMWG I-Ds
<draft-ietf-bmwg-bgpbas-01.txt>, Pending term. progress
<draft-ietf-bmwg-benchres-method-00.txt> Pending term progress

New Work proposals.
* Protection  benchmarking - need to clarify ... See meeting notes from 
IETF-58, IETF-57 and earlier...
* Considerations for Measuring Network Convergence, is BMWG the home for this?
* Suggestion for MPLS-LDP convergence benchmarking (in future)

RFC Editor

Charter Update
Revising Milestones.

New RFC:

FYI - Important dates for IETF-59 may be found at

Please direct comments on the status to BMWG list, or to the chairs:
Kevin Dubray <kdubray@juniper.net> and Al Morton <acmorton@att.com>

bmwg mailing list