Re: [93attendees] Meeting schedule

Jari Arkko <jari.arkko@piuha.net> Tue, 21 July 2015 22:37 UTC

Return-Path: <jari.arkko@piuha.net>
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 9E53A1B29C9 for <93attendees@ietfa.amsl.com>; Tue, 21 Jul 2015 15:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 pFuEEMDFa7ql for <93attendees@ietfa.amsl.com>; Tue, 21 Jul 2015 15:37:56 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id AE2301A0381 for <93attendees@ietf.org>; Tue, 21 Jul 2015 15:37:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 040EE2CC5D for <93attendees@ietf.org>; Wed, 22 Jul 2015 01:37:54 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFEAzL6dwsBe for <93attendees@ietf.org>; Wed, 22 Jul 2015 01:37:53 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5CD5E2CC49 for <93attendees@ietf.org>; Wed, 22 Jul 2015 01:37:53 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_43B1E01E-120A-465F-81C0-BCF400802D75"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Pgp-Agent: GPGMail 2.5
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9DEC79C9-F117-453A-8F8F-98BA0FC62B08@cs.ucla.edu>
Date: Wed, 22 Jul 2015 00:37:52 +0200
Message-Id: <822C7233-3ACC-4A03-A556-C907CF90684A@piuha.net>
References: <p06240602d1d3231e977e@[130.129.14.251]> <670E6EB2-3519-4B5A-B5BD-D323E15033D7@cs.ucla.edu> <p06240613d1d407147bfb@[130.129.14.251]> <9DEC79C9-F117-453A-8F8F-98BA0FC62B08@cs.ucla.edu>
To: 93attendees@ietf.org
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/-YOTypqSTulth5ib8eGYCo-zP70>
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 22:37:58 -0000

Thanks for an interesting discussion. FWIW, I think the IESG / IAOC are looking at these
discussions so maybe we can just have it on this list.

First, I wanted to highlight that this week’s schedule wrt the morning plenaries is an experiment.
The lunch break allows the room setup conversion to take place without disturbing our meeting
time.

We’ve discussed the plenaries in the IESG/IAB Sunday meeting, and are considering a joint,
shorter (¨2.5h) plenary for IETF-94. This would further compress the time that we use for
reporting, but should still allow a brief(er) technical topic to be discussed and some amount
of time for asking questions from the leadership boards. The saved time could be used
for working group meetings, breaks for those important side discussions or that important
rest. This is like we had it some years ago, but it would be an experiment to see how it
works in today’s IETF.

Thoughts?

Also, we are very acutely aware of the tradeoffs between adequate rest in an intense week,
time for the WGs to do their interesting work, time for the unofficial and unscheduled discussions
to happen, and the constraints on lengthening the week. We have always tried to balance
these, and feedback on where we are with that is very much appreciated.

Part of the reason that we have such an intense meeting this time is that there are
so many working groups and that people find interesting work to do. I think that’s
good. It is also a good thing that many of the most active WGs are using virtual
interim meetings to progress their work.

There are no magic solutions to offer more time; don’t think we can extend the week.
We’ll just have to do even more between meetings, use time even smarter in the
meetings, and use more parallelism.

Jari