Guidelines for IETF 111 session requests
Lars Eggert <chair@ietf.org> Thu, 15 April 2021 15:32 UTC
Return-Path: <chair@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 225063A2438
for <wgchairs@ietfa.amsl.com>; Thu, 15 Apr 2021 08:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 pTelAJCv9KsT for <wgchairs@ietfa.amsl.com>;
Thu, 15 Apr 2021 08:32:55 -0700 (PDT)
Received: from stickers.eggert.org (mail.eggert.org [91.190.195.94])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPSA id AD5E33A2435
for <wgchairs@ietf.org>; Thu, 15 Apr 2021 08:32:54 -0700 (PDT)
From: Lars Eggert <chair@ietf.org>
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Subject: Guidelines for IETF 111 session requests
Message-Id: <4B8970B4-D104-4A8D-A69F-91B3BAC812FD@ietf.org>
Date: Thu, 15 Apr 2021 18:32:51 +0300
To: wgchairs@ietf.org
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/_x2nc9Xqa5i1U4SuEFs3eggTCyk>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>,
<mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>,
<mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Apr 2021 15:32:56 -0000
Hi, the IESG and the IRTF Chair believe there is value for most working and research groups to have a session during IETF meetings, to encourage interchange of ideas with the broadest possible audience. While we would love to be able to give every WG all the time that they’d need, we have very clear feedback that a remote meeting that extends beyond five days or six hours per day is challenging for participants. This means that there is less meeting time available during remote meetings than during in-person meetings. While more meeting time can be added by going beyond eight simultaneous tracks, this increases the potential for conflicts when sessions are scheduled in the same slot. IETF 110 was scheduled with nine parallel tracks, and meeting feedback indicated that the community noticed an increase in conflicts. In light of this tension, and in preparation for IETF 111 as a likely remote meeting, we ask that you consider the following guidelines as you decide how to make your session requests for IETF 111, which will become possible on April 26: * If your WG or RG needs more than two hours of meeting time, please consider structuring the agenda so that work items that benefit most from broad community exposure (e.g., new work, rechartering, adoption calls) take place in a single session at IETF 111, and schedule interim meetings for all other work items. Note that you are allowed to schedule interim meetings for the week after IETF meetings but not the week before, nor during, the IETF meeting week. * Requests for more than two hours of total meeting time are discouraged. In special cases, you may request more than two hours of meeting time, but we will likely request a rationale, and scheduling pressure may still make it impossible to grant any additional meeting slots. * If you request a single two-hour session, we encourage you to mention in the comments of the session request if it’s OK to split the time into two separate 1-hour sessions. This substantially increases the scheduling degrees of freedom to reduce conflicts. * We also request you to carefully review your list of conflicts, instead of simply copying the previous meeting’s list. Inaccurate conflict reporting creates real conflicts. * Finally, as always, please try your best to estimate the meeting time your WG will need, because requesting more time than needed increases agenda pressure. Lars Eggert IETF Chair (on behalf of the IESG)
- Guidelines for IETF 111 session requests Lars Eggert
- Re: Guidelines for IETF 111 session requests Michael Richardson
- Re: [irsg] Guidelines for IETF 111 session reques… Lars Eggert