Re: [93attendees] Meeting schedule

Lixia Zhang <lixia@cs.ucla.edu> Tue, 21 July 2015 14:15 UTC

Return-Path: <lixia@cs.ucla.edu>
X-Original-To: 93attendees@ietfa.amsl.com
Delivered-To: 93attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 771201A8880 for <93attendees@ietfa.amsl.com>; Tue, 21 Jul 2015 07:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RhYOlt0yhgfF for <93attendees@ietfa.amsl.com>; Tue, 21 Jul 2015 07:15:48 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC531A8858 for <93attendees@ietf.org>; Tue, 21 Jul 2015 07:15:48 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 16D06A60004; Tue, 21 Jul 2015 07:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36RNalR-wqM1; Tue, 21 Jul 2015 07:15:47 -0700 (PDT)
Received: from dhcp-89c6.meeting.ietf.org (dhcp-89c6.meeting.ietf.org [31.133.137.198]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id BAEDCA60002; Tue, 21 Jul 2015 07:15:46 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <p06240602d1d3231e977e@[130.129.14.251]>
Date: Tue, 21 Jul 2015 07:15:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <670E6EB2-3519-4B5A-B5BD-D323E15033D7@cs.ucla.edu>
References: <p06240602d1d3231e977e@[130.129.14.251]>
To: Randall Gellens <rg+ietf@qti.qualcomm.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/I3kUUxzbptnuVM5Qr5DgYDqr1uI>
Cc: 93attendees@ietf.org
Subject: Re: [93attendees] Meeting schedule
X-BeenThere: 93attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 93 attendees that have opted in on this list. " <93attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/93attendees>, <mailto:93attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/93attendees/>
List-Post: <mailto:93attendees@ietf.org>
List-Help: <mailto:93attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/93attendees>, <mailto:93attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 14:15:49 -0000

> On Jul 20, 2015, at 3:16 PM, Randall Gellens <rg+ietf@qti.qualcomm.com> wrote:
> 
> The meeting schedule, in my view, runs too late in the evening. Tonight's session ended at 7:50 PM, meaning it was 8:15 before one could even start trying to go to dinner.  This means it's 9:00 before one is able to eat, which in my view, is far too late.  I know people hated the old-old schedule that went until 10, but at least that had a dinner break at a 6:00, a reasonable hour; if we absolutely must go late, that was a better way to do it.  The schedule this time forces people to either try to sleep on a full stomach (which I can't do), skip dinner, or stay up way late and be sleep-deprived, fueled by caffeine and adrenaline (which I think makes for very bad meetings and bad technical work).

In the spirit of brainstorm, here is my 2 cents:

1/ if making the room arrangement is an issue, why dont we minimize this hassle by doing it once instead of twice?

i.e. running IAB and IESG plenary back-to-back.

2/ we can devote either one morning or one afternoon to it.
(I think morning would be better, so that there is lunch break to re-arrange the room; if afternoon, then there is still this issue of re-arrange the room quick so that we can have WG meetings after that).

3/ if morning but 2.5 hours looks a bit short: start at 8:30AM, and/or run to 12:00?
Given IETF covers breakfast one way or the other, this does not suffer from the food quality concerns as some people expressed regarding doing a plenary over lunch time.

Lixia

PS: haven't had time to read all the msgs on this thread, so forgive me if the idea is already mentioned.