[bmwg] Fwd: Tentative Agenda for BMWG at IETF-57

Al Morton <acmorton@att.com> Mon, 07 July 2003 18:53 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07704 for <bmwg-archive@lists.ietf.org>; Mon, 7 Jul 2003 14:53:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zb6j-0004tD-2d; Mon, 07 Jul 2003 14:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zb6H-0004sj-NQ for bmwg@optimus.ietf.org; Mon, 07 Jul 2003 14:52:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07673 for <bmwg@ietf.org>; Mon, 7 Jul 2003 14:52:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zb6F-0000mr-00 for bmwg@ietf.org; Mon, 07 Jul 2003 14:52:31 -0400
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 19Zb6E-0000mV-00 for bmwg@ietf.org; Mon, 07 Jul 2003 14:52:30 -0400
Received: from attrh2i.attrh.att.com ([135.37.94.56]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h67Ipegc023657 for <bmwg@ietf.org>; Mon, 7 Jul 2003 13:52:00 -0500
Received: from custsla.mt.att.com (135.21.14.109) by attrh2i.attrh.att.com (6.5.019) id 3EEC9931005CAF3F for bmwg@ietf.org; Mon, 7 Jul 2003 14:51:30 -0400
Received: from acmortonw.att.com (acmortonw.mt.att.com [135.16.251.24]) by custsla.mt.att.com (8.10.2+Sun/8.10.2) with ESMTP id h67J3tq04962 for <bmwg@ietf.org>; Mon, 7 Jul 2003 15:03:55 -0400 (EDT)
Message-Id: <5.2.1.1.0.20030707144848.0672bb70@custsla.mt.att.com>
X-Sender: acm@custsla.mt.att.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 07 Jul 2003 14:51:55 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [bmwg] Fwd: Tentative Agenda for BMWG at IETF-57
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>
Content-Transfer-Encoding: quoted-printable

Here's the tentative meeting agenda we submitted today.
Comments by June 8th 8:30 AM EDT, please.

thanks, and sorry for the short turn-around,
Al


>---------------------------------------
>
>Benchmarking Methodology WG (bmwg)
>
>Tuesday, July 15, 2003, 1300-1400 and 1415-1515
>=======================================
>
>CHAIRS: Kevin Dubray <kdubray@juniper.net>
>         Al Morton <acmorton@att.com>
>
>AGENDA:
>
>1.   Working Group Status (Morton)
>
>2.   [Tentative] Discussion on OSPF Convergence Benchmarking WG Last
>      Call comments. Last call is over, but a few comments need
>      discussion.  Identification of remaining issues.  (R. White et al.)
>
>http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-term-04.txt
>http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-intraarea-05.txt
>http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-applicability-03.txt
>      BMWG mail archive:
>      http://www.ietf.org/mail-archive/working-groups/bmwg/current/
>      Unofficial versions with latest comment resolutions are here:
>      http://www.riw.us/ospf-benchmark/
>
>
>3.  Benchmarking Network-layer Traffic Control Mechanisms:
>     Terminology -- Communicate latest changes & test progress of
>     current WG Last Call. (J. Perser et al.)
>
>     http://www.ietf.org/internet-drafts/draft-ietf-bmwg-dsmterm-07.txt
>
>     Also: New Draft on Benchmarking Traffic Control Mechanisms:
>     Methodology -- Brief introduction and identify areas for comment
>     and contribution during development. (J. Perser et al.)
>
>4.  [Tentative spot for conterm-05]
>
>5.  IPsec Device Benchmarking Terminology I-D. New material in 01.
>     Questions, issues, or areas for where commentary is desired.  (M. Kaeo)
>
>     http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ipsec-term-01.txt
>
>
>6.  IGP Data plane convergence benchmark I-Ds. Brief introduction of new
>     work item. Questions, issues, or areas for where commentary is desired.
>     (S.Poretsky)
>
>http://www.ietf.org/internet-drafts/draft-ietf-bmwg-igp-dataplane-conv-term-00.txt
>http://www.ietf.org/internet-drafts/draft-ietf-bmwg-igp-dataplane-conv-meth-00.txt
>http://www.ietf.org/internet-drafts/draft-poretsky-igp-convergence-app-00.txt
>
>
>2nd Session
>Tuesday, July 15, 2003, 1415-1515
>=======================================
>
>7.  Resource Reservation Terminology benchmark I-Ds. Description of changes
>     based on review. Questions, issues, areas for input. (Fehér Gábor Gume)
>
>http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-bmwg-benchres-term-03.txt
>
>
>8.  Terminology for Benchmarking Core Router Accelerated Life Testing.
>     What is the level of readership? Comments? (S. Poretsky et al.).
>
>http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-bmwg-acc-bench-term-00.txt
>
>9.  Revised Milestones -- a growing list. (Morton)
>
>
>10. New work proposal: Automatic Protection Switching Benchmark Terminology
>     The WG has discussed this item at several previous meetings.
>     Is the BMWG the right home for this I-D? The Goal has been articulated
>     as follows:
>
>     The objective of this effort is to produce a terminology and
>     methodology set of drafts that specifies the performance
>     benchmarking sub-IP layer resiliency and protection technologies.
>     There is a common terminology draft and multiple methodology drafts
>     for the technologies.  The methodology drafts will include (but not
>     limited to) Automatic Protection Switching (APS) for SONET/SDH,
>     Fast Reroute for Multi-Protocol Label Switching (MPLS), and
>     Resilient Packet Ring (RPR) standardized in IEEE. (T.Kimura, J.Perser)
>
>http://www.ietf.org/internet-drafts/draft-kimura-protection-term-01.txt
>
>     Related Individual Draft on MPLS Protection Benchmarking Methodology
>     (S.Poretsky, et al.)
>
>http://www.ietf.org/internet-drafts/draft-poretsky-mpls-protection-meth-00.txt
>
>XX.  Other Drafts
>http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-bmwg-conterm-05.txt
>
>Please help contribute to a successful meeting by reading the above
>I-D(s) and references *before* we meet.
>
>To offer comments on BMWG work in progress or the agenda itself,
>please send email to:
>
>             bmwg@ietf.org
>
>Alternatively, to offer potential agenda items, please email:
>
>             kdubray@juniper.net and acmorton@att.com


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