IETF Logo Mail Archive

RE: Proposed WG and BOF Scheduling Experiment

"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 08 November 2010 10:51 UTC

Return-Path: <dworley@avaya.com>
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 9AFAF3A6997 for <ietf@core3.amsl.com>; Mon, 8 Nov 2010 02:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, 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 5QEeh78puvuM for <ietf@core3.amsl.com>; Mon, 8 Nov 2010 02:51:15 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 75A503A6978 for <ietf@ietf.org>; Mon, 8 Nov 2010 02:51:15 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGpk10zGmAcF/2dsb2JhbACiBHGjSgKYaIVIBIRYiSA
X-IronPort-AV: E=Sophos;i="4.58,313,1286164800"; d="scan'208";a="217506493"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 Nov 2010 05:51:35 -0500
X-IronPort-AV: E=Sophos;i="4.58,313,1286164800"; d="scan'208";a="537883092"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 Nov 2010 05:51:34 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Mon, 8 Nov 2010 05:51:33 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Russ Housley <housley@vigilsec.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 08 Nov 2010 05:49:47 -0500
Subject: RE: Proposed WG and BOF Scheduling Experiment
Thread-Topic: Proposed WG and BOF Scheduling Experiment
Thread-Index: Act/LtId5AAtETxcTO6jFOgehusvzQAA9bS2
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22022889E8@DC-US1MBEX4.global.avaya.com>
References: <20101108022649.BD7E03A694D@core3.amsl.com> <4CD76710.7050004@gmail.com>, <1638.210.138.216.50.1289211674.squirrel@mail.smetech.net>
In-Reply-To: <1638.210.138.216.50.1289211674.squirrel@mail.smetech.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
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:51:16 -0000

________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of Russ Housley [housley@vigilsec.com]

The deadline for BOF requests comes too soon after the end of one IETF
meeting for the next one.  We are hearing complaints, and subjectively,
the quality of the request write-ups do reflect this situation.  So, yes,
the intent is to allow more time by shifting the BOF request deadline.
_________________________________________

I would think that the more formal the session, the longer in advance that the need for the session will be reliably predicted.  Since BOFs are less formal, the deadline for them should be *later* than for WG sessions, preferably very shortly before the IETF meeting.

Dale

v2.23.0 | Report a Bug | By Email