[bmwg] Draft Agenda for BMWG at IETF-68

Al Morton <acmorton@att.com> Wed, 07 March 2007 09:04 UTC

Return-path: <bmwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOs4o-0006vm-0N; Wed, 07 Mar 2007 04:04:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOize-0005ZM-3f for bmwg@ietf.org; Tue, 06 Mar 2007 18:22:54 -0500
Received: from mail120.messagelabs.com ([216.82.250.83]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HOhQM-0005Sf-KR for bmwg@ietf.org; Tue, 06 Mar 2007 16:42:27 -0500
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-8.tower-120.messagelabs.com!1173217340!12041141!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 20350 invoked from network); 6 Mar 2007 21:42:21 -0000
Received: from unknown (HELO attrh0i.attrh.att.com) (134.24.146.4) by server-8.tower-120.messagelabs.com with SMTP; 6 Mar 2007 21:42:21 -0000
Received: from attrh.att.com (localhost [127.0.0.1]) by attrh0i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l26LgGbT003956 for <bmwg@ietf.org>; Tue, 6 Mar 2007 16:42:16 -0500 (EST)
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by attrh0i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l26LgCdP003919 for <bmwg@ietf.org>; Tue, 6 Mar 2007 16:42:12 -0500 (EST)
Message-Id: <200703062142.l26LgCdP003919@attrh0i.attrh.att.com>
Received: from acmt.att.com (acmt.mt.att.com[135.16.251.81](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20070306214211gw10010gjoe>; Tue, 6 Mar 2007 21:42:11 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 06 Mar 2007 16:41:19 -0500
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Subject: [bmwg] Draft Agenda for BMWG at IETF-68
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: bmwg-bounces@ietf.org

BMWG:

I've just uploaded the draft agenda (below),
comments/omissions/bashing welcome.

I'd like to finalize the presenters and receive
slides by March 16th. You can revise your slides
once (before the 20th).

Folks who will be present should volunteer for the
important roles below (or I will pick *you*):
Official Note Taker
Back-up Note Taker
Jabber Room Comment Reader*

Al
bmwg co-chair

* this person can interrupt the line to read jabber comments,
and since we're meeting at a somewhat friendly time for US time
zones, I expect that there will be some remote participation.

-------------------------------------------------------------------------

Benchmarking Methodology WG (bmwg)
==================================
TUESDAY, March 20, 2007
1300-1500 Afternoon Session I
Karlin I
==================================

CHAIR(s): Al Morton <acmorton@att.com>

DRAFT Agenda

0.  Agenda bashing (if we need to shuffle a few items)
     See 
https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=68
     for Agenda updates and Slides

1.  Working Group Status (Chair)
     draft-ietf-bmwg-hash-stuffing-08    	RFC Ed Queue
     see http://tools.ietf.org/wg/bmwg/ for status of other drafts

2.  IPv6 Benchmarking Methodology   (Chip Popoviciu)
     draft-ietf-bmwg-ipv6-meth-01
Results from WGLC: close on any open issues

3.  Benchmarking Protection Mechanisms  (Rajiv or Jay)
     draft-ietf-bmwg-protection-meth-01  	
     draft-ietf-bmwg-protection-term-00
Need discussion to close on previous issues raised, such as whether a 
loss-based
recovery time determination is sufficient for protection mechanisms.
Editorial review of the entire methodology; changes to the text include:
Refined Intro to improve the flow of the document
Deleted figure 4.9 and reduced number of test cases to 2 in section 5.5

4.  Benchmarking Resource Reservation Mechanisms  (Krisztian Nemeth)
     draft-ietf-bmwg-benchres-term-08    	RFC Ed Queue
What was accomplished, what is ahead...

5.  Milestone Status (Chair)


*******   New Work Proposals  *********


6.  New Proposal Summary (Chair)

7.  LDP Convergence Benchmarking Terms and Methodology (Thomas, Rajiv or Jay)
     draft-eriksson-ldp-convergence-term-04
     draft-karthik-bmwg-ldp-convergence-meth-00
Added new term  LDP Advertisement Type
First draft of methodology to complement terms

8.  MPLS VPN Scalability Benchmarking  (Silvija Dry)
     draft-sdry-bmwg-mvpnscale-01
- Update on changes in the "01" version
- Agree on the scope of the draft

9.  Bidirectional Forwarding Detection Benchmarking  (Esa or Jay)
     draft-salahuddin-bmwg-bfd-motivation-00
The BFD protocol is becoming an increasingly popular alternative to a
variety of existing methods to detect forwarding failures on links between
network elements. It is being proposed as the forwarding failure detection
mechanism for a host of routing protocols, virtual links and p2mp topologies.
It is a very useful in the situations where underlying physical media doesn't
lend itself well to fast detection of failures.

You can find extensive information on the BFD protocol itself at the 
BFD WG weblink
http://tools.ietf.org/wg/bfd/


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