Re: Proposed WG and BOF Scheduling Experiment
"Spencer Dawkins" <spencer@wonderhamster.org> Mon, 08 November 2010 10:49 UTC
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5407E3A6978; Mon, 8 Nov 2010 02:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.114
X-Spam-Level:
X-Spam-Status: No, score=-101.114 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, TVD_FINGER_02=2.134, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ky6lbk8y+i6q; Mon, 8 Nov 2010 02:49:35 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 8D00F3A69BD; Mon, 8 Nov 2010 02:49:35 -0800 (PST)
Received: from S73602b (dhcp-771c.meeting.ietf.org [130.129.119.28]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LngZT-1Obw0r2BdH-00hmvn; Mon, 08 Nov 2010 05:49:54 -0500
Message-ID: <A633E4B821DC48EFA71FC7D12A5AB5CF@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: Michael Richardson <mcr@sandelman.ca>, wgchairs@ietf.org, ietf@ietf.org
References: <20101108022649.BD7E03A694D@core3.amsl.com><4CD7607E.8030705@bbn.com><C58676BCA8DD4B818C8AA5778ECBAB18@23FX1C1><AANLkTikusNxxhQA4WOjEiLZfRLR0EjG3=0mViKdq7pjQ@mail.gmail.com><4CD78986.6010502@ripe.net> <24819.1289209423@marajade.sandelman.ca>
Subject: Re: Proposed WG and BOF Scheduling Experiment
Date: Mon, 08 Nov 2010 04:49:29 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="Windows-1252"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-Provags-ID: V02:K0:eqfbmWdrgwGAqQKRWO2mBLHhyQEaraCB5BeGmO4goxK E/ODG7Bnryle+/YA43GtV6LaWynHh9oppKKj0g4QKwG6HQwPal rNOwL/0hImfBgZCVkwRXkAVO2iEIy8YlvLqCCMJBuqnWCYfQeu rF7Avq58HOwbL3mD44d1iNEJC9Y50B8R3Ofy4JRiSSd70klM9t Lvz3a0KeR7FaNzb3hCzzkQSwpvesYmHR5pC7APC/gg=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 10:49:36 -0000
Assuming, of course, that we continue to expect that the IESG will "do the right thing, whatever that turns out to be" ... >>>>>> "Henk" == Henk Uijterwaal <henk@ripe.net> writes: > Henk> So, I'd take it a step further: Starting Monday morning, 2 of the > 7 > Henk> or 8 meeting slots in each session are reserved for BOFs and the > other > Henk> 4 or 5 for WG meetings. That way, we'll have all the BOFs done > by > Henk> Tuesday lunchtime, giving time to discuss the results during the > week, > Henk> and impact on the rest of the schedule is minimal. > > I think this is the best idea. I agree with this - front-load the BOFs, but not to the point where they collide with related BOFs ("do the right thing, whatever that turns out to be" ...) > If the rooms for the BOFs are clearly identified, then we can also > easily give the BOFs 1hr slots rather than the 2.5 hour slots that > occurs most mornings. My understanding of what BOFs are supposed to do, is that WG-forming BOFs should be demonstrating that there is a group of people who will do the work described in a proposed charter, and that they roughly agree that the proposed charter describes what they want to do. If that's so, we should rarely have a WG-forming BOF that runs over an hour - and if THAT'S so, it will be easier to schedule BOFs early in the week without colliding with other BOFs. The "bunch of people get together and talk" kind of BOF don't need to be so constrained on time - I'm focused on WG-forming BOFs when I say this. Thanks, Spencer
- Proposed WG and BOF Scheduling Experiment The IESG
- Re: Proposed WG and BOF Scheduling Experiment Richard L. Barnes
- Re: Proposed WG and BOF Scheduling Experiment Dave CROCKER
- Re: Proposed WG and BOF Scheduling Experiment Scott Brim
- Re: Proposed WG and BOF Scheduling Experiment Brian E Carpenter
- Re: Proposed WG and BOF Scheduling Experiment Aaron Falk
- Re: Proposed WG and BOF Scheduling Experiment Geoff Mulligan
- Re: Proposed WG and BOF Scheduling Experiment Phillip Hallam-Baker
- Re: Proposed WG and BOF Scheduling Experiment Barry Leiba
- Re: Proposed WG and BOF Scheduling Experiment Henk Uijterwaal
- RE: Proposed WG and BOF Scheduling Experiment gregory.cauchie
- Re: Proposed WG and BOF Scheduling Experiment Michael Richardson
- RE: BOF Attendance Minimization Bernard Aboba
- Re: Proposed WG and BOF Scheduling Experiment Russ Housley
- Re: Proposed WG and BOF Scheduling Experiment Pete Resnick
- Re: BOF Attendance Minimization Dave CROCKER
- Re: Proposed WG and BOF Scheduling Experiment Andrew Sullivan
- Re: Proposed WG and BOF Scheduling Experiment Spencer Dawkins
- RE: Proposed WG and BOF Scheduling Experiment Worley, Dale R (Dale)
- RE: Proposed WG and BOF Scheduling Experiment Ross Callon
- Re: Proposed WG and BOF Scheduling Experiment Kurt Zeilenga
- Provider-Aggregated vs Provider-Independent IPv6 … Templin, Fred L
- Re: Provider-Aggregated vs Provider-Independent I… Brian E Carpenter
- Re: Proposed WG and BOF Scheduling Experiment Geoff Mulligan
- RE: Proposed WG and BOF Scheduling Experiment David Harrington
- Re: Proposed WG and BOF Scheduling Experiment Andrew G. Malis
- Re: Proposed WG and BOF Scheduling Experiment Scott Brim
- RE: Proposed WG and BOF Scheduling Experiment Worley, Dale R (Dale)
- Re: Proposed WG and BOF Scheduling Experiment Eric Burger