Re: [Ietf-hub-boston] Future meeting schedule

worley@ariadne.com (Dale R. Worley) Wed, 06 November 2019 23:53 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf-hub-boston@ietfa.amsl.com
Delivered-To: ietf-hub-boston@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4796912009C for <ietf-hub-boston@ietfa.amsl.com>; Wed, 6 Nov 2019 15:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level:
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEikKb1rFVSD for <ietf-hub-boston@ietfa.amsl.com>; Wed, 6 Nov 2019 15:53:34 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 079CA120052 for <ietf-hub-boston@ietf.org>; Wed, 6 Nov 2019 15:53:33 -0800 (PST)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id SKwXibJExuFiMSV7EieY04; Wed, 06 Nov 2019 23:53:32 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1573084412; bh=FLMLta288KzOSa5UV+J4Sj8PXVmFGE5YIehSQOfdSO8=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=phtAd98LToYm3adHElreU3Znza9I14p4RjKJxu/M8TznUsNJfkf4Z3uLQ9fVjPLA+ y7WPqzrjkfNN2jgbJ4puYo7mKubwQvLWj3kH25QNoJAmhHBDZ3qsTjLnZlyY2+hyFF SLR1ILZhz08/kJzuBUixWdB2G9X6VxWc1AdHP0WX/YrRMDagh8eC21eoqmfY3jb1Yq bDI9z3lX+uOuX4M6eat8A8E652TOxS4RsDXe2yuu54ofKesKouVIR+tQF7+kmMbGwt T4tXKVy9evE5+97lOz7O3pSFaQyMV3CIWQHX+/iLH+ZN1Iu3tFQ0PxiFzZMModKiDF BJTPqbsK0A6lg==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with ESMTPA id SV7DiK39L6b3JSV7Ei5dNu; Wed, 06 Nov 2019 23:53:32 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id xA6Ns5jH009451 for <ietf-hub-boston@ietf.org>; Wed, 6 Nov 2019 18:54:05 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id xA6Ns4W3009448; Wed, 6 Nov 2019 18:54:04 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: ietf-hub-boston@ietf.org
In-Reply-To: <8736f4a3z9.fsf@hobgoblin.ariadne.com> (worley@ariadne.com)
Sender: worley@ariadne.com
Date: Wed, 06 Nov 2019 18:54:04 -0500
Message-ID: <87imnw8stf.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-hub-boston/sGWtyPuR_NvUxroZBB0h5bdCi2U>
Subject: Re: [Ietf-hub-boston] Future meeting schedule
X-BeenThere: ietf-hub-boston@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "For IETFers in the Boston area." <ietf-hub-boston.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-hub-boston>, <mailto:ietf-hub-boston-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-hub-boston/>
List-Post: <mailto:ietf-hub-boston@ietf.org>
List-Help: <mailto:ietf-hub-boston-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-hub-boston>, <mailto:ietf-hub-boston-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 23:53:35 -0000

For "conference style" meetings, I'm assuming, say, running it from 5 to
7pm, with dinner afterward.  This could be split into 4 30-minute
segments or 6 20-minute segments.  OTOH, we could run it from 5 to 8pm,
and have 6 30-minute segments.

One question is how hard it is to get speakers.  Having never done that
for IETF Hub, I don't know how many people have pent-up discussions to
present.

In regard to effort level, I assume that for most people, most of the
effort is travel and allocating the time.  But maybe the shorter format
of a simple dinner gettogether is much easier for people to schedule.

Opinions?

Dale