[rgchairs] Long BoFs (was Re: 63rd IETF Agenda - DRAFT)

Rohan Mahy <rohan@ekabal.com> Wed, 20 July 2005 17:00 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvHw0-0008Vh-F6; Wed, 20 Jul 2005 13:00:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvHvy-0008SM-HY; Wed, 20 Jul 2005 13:00:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09190; Wed, 20 Jul 2005 13:00:34 -0400 (EDT)
Received: from figas.ekabal.com ([204.61.215.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvIPo-0001N2-KL; Wed, 20 Jul 2005 13:31:30 -0400
Received: from [131.161.248.88] (open-131-161-248-88.cliq.com [131.161.248.88]) (authenticated) by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id j6KH0XE12830; Wed, 20 Jul 2005 10:00:33 -0700
In-Reply-To: <20050714151118.GB18322@1-4-5.net>
References: <E1Ds6Ih-000461-Sk@newodin.ietf.org> <28691ceb6e3bab25470b527e8b450efe@telio.no> <20050714151118.GB18322@1-4-5.net>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4b42969153c704fc78e507c457d1aab6@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Date: Wed, 20 Jul 2005 10:00:24 -0700
To: Working Group Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: rgchairs@irtf.org, bofchairs@ietf.org, IETF Secretariat <ietf-secretariat-reply@ietf.org>
Subject: [rgchairs] Long BoFs (was Re: 63rd IETF Agenda - DRAFT)
X-BeenThere: rgchairs@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IRTF research group chairs list <rgchairs.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rgchairs>
List-Post: <mailto:rgchairs@lists.ietf.org>
List-Help: <mailto:rgchairs-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=subscribe>
Sender: rgchairs-bounces@lists.ietf.org
Errors-To: rgchairs-bounces@lists.ietf.org

Folks,

I understand that voipeer was approved and the ADs agreed on 2.5 hours. 
  My personal impression is that if a BoF requires more than 1 hour, 
either the scope is too large or there has not been enough mailing list 
or ad-hoc discussion yet.

I think the scheduling problem would be easier if we restrict BoFs to 1 
hour in the future.  Active WGs should take precedence and this is one 
way to do that.

Thanks again Marcia for making the best of an impossible situation.

thanks,
-rohan

On Jul 14, 2005, at 8:11, David Meyer wrote:
> On Thu, Jul 14, 2005 at 04:33:00PM +0200, Hisham Khartabil wrote:
>> There is a conflict in the agenda on Thursday Afternoon Session I. A
>> sizeable portion on the VoIP community attend SIMPLE WG meeting and
>> will be interested in attending VOIPEER BOF.
>>
>> It would be great that when moving the slot, to make sure that no 
>> other
>> conflicts occur with sip, sipping, enum, mmusic, ecrit, xcon, behave
>> and avt working groups. It might be much easier to move voipeer since
>> its a bof and I dont think it requires a 2.5 hour slot.
>
> 	First, I realize the very difficult scheduling problem
> 	that the secretariat is facing. I wanted, however, to
> 	address the time requirements for the BOF. When I was
> 	discussing this with the ADs, we settled on this length
> 	for the BOF due to the overwhelming number of folks who
> 	expressed interest in participating (and their various
> 	scheduling constraints). In any event, I would rather
> 	leave the 2.5 hour length as it is, or we won't be able
> 	to have time for everyone who has expressed interest to
> 	participate, and to have a reasonable amount of time for
> 	discussion.
>
> 	Dave


_______________________________________________
Rgchairs mailing list
Rgchairs@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/rgchairs