Re: [Manycouches] Follow up on consultation on planning for IETF 111
John C Klensin <john-ietf@jck.com> Thu, 08 April 2021 01:07 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419CC3A317A; Wed, 7 Apr 2021 18:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 vBlZj-Sc52ll; Wed, 7 Apr 2021 18:07:23 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 978803A3145; Wed, 7 Apr 2021 18:07:18 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lUJ8f-000DSW-4M; Wed, 07 Apr 2021 21:07:17 -0400
Date: Wed, 07 Apr 2021 21:07:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jay Daley <jay@ietf.org>
cc: admin-discuss@ietf.org, manycouches@ietf.org
Message-ID: <48A49DC52712A1E9BC63110A@PSB>
In-Reply-To: <FD6DB75C-9787-40C1-B8F4-B6C57010F957@ietf.org>
References: <3431E359-7CDE-43AE-9284-56A9C0AC3A1A@ietf.org> <51D8C896A46BBB1BFFCFEB37@PSB> <FD6DB75C-9787-40C1-B8F4-B6C57010F957@ietf.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/V6B_9NFeBWv1uDu6pCZLj9dOxas>
Subject: Re: [Manycouches] Follow up on consultation on planning for IETF 111
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of remote meeting attendance and virtual IETF meetings, as well as for SHMOO working group" <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 01:07:28 -0000
--On Thursday, April 8, 2021 07:36 +1200 Jay Daley <jay@ietf.org> wrote: > > >> On 8/04/2021, at 6:22 AM, John C Klensin <john-ietf@jck.com> >> wrote: >> >> Jay, >> >> This looks entirely reasonable. Two small comments below >> (with most of the rest of your note elided to save space)... >> >> --On Wednesday, April 7, 2021 09:43 +1200 Jay Daley >> <jay@ietf.org> wrote: >> >>> The consultation on proposals regarding planning for IETF 111 >>> finished on 2 April. Several points were raised and are >>> paraphrased and addressed as follows: >>> ... >>> d. Consider hybrid meetings >>> This work has now started, but potentially targeting IETF 112 >>> not IETF 111 given the work required >> >> Just to clarify, this means that, for IETF 111, the meeting >> will either be all-remote or. while remote participation will >> be allowed and encouraged (as it has been for decades), the >> expectation is that most participation will be f2f. Is that >> correct? > > In order to consider a 'hybrid' meeting we will need to change > the assessment criteria to increase the threshold for those > that can be generalised as "If 20% or more cannot attend for X > reason then we cannot meet". I don't know yet what the > replacement for 20% will be, nor what the community would find > acceptable for X. For example, as it currently stands nobody > from the EU can travel to the US easily taking us over the 20% > threshold. If we say increased the 20% to 50% then would > people find it acceptable to hold a hybrid meeting under such > circumstances? Sorry, did not mean to draw you back into a discussion about how we would decide to have a hybrid meeting -- I think that has been covered more than adequately for now and hope we can have that conversation at a more convenient time and, as you said, for IETF 112. I was just trying to understand your definition of "hybrid meeting" a little better and, in particular, what the difference is between your definition of a hybrid meeting and every meeting in at least a couple of decades prior to IETF 107. I note in particular that IETF 102 through IETF 106 each had more than 1/3 remote participants. Consequently, if we could magically go back to the middle of 2018 and magically apply perfect foresight and today's 80% criterion to them, all of those meetings would have been forced to be fully remote. Obviously (I hope) that not only is impossible but would have been stupid. I just want to be sure that we don't think about "hybrid meeting" in a way that would discard the precedents and experience of many years in which a significant number of participants were remote. Or, if we are going to move forward in a way that is ultimately equivalent to "some participants are more significant, important, or equal than others" that we be very explicit about that. john
- [Manycouches] Follow up on consultation on planni… Jay Daley
- Re: [Manycouches] Follow up on consultation on pl… Salz, Rich
- Re: [Manycouches] Follow up on consultation on pl… John C Klensin
- Re: [Manycouches] Follow up on consultation on pl… Jay Daley
- Re: [Manycouches] Follow up on consultation on pl… John C Klensin
- Re: [Manycouches] Follow up on consultation on pl… Alexandre Petrescu
- Re: [Manycouches] [admin-discuss] Follow up on co… Livingood, Jason
- Re: [Manycouches] [admin-discuss] Follow up on co… Brian E Carpenter
- Re: [Manycouches] [admin-discuss] Follow up on co… John C Klensin
- Re: [Manycouches] [admin-discuss] Follow up on co… Michael Richardson
- Re: [Manycouches] [admin-discuss] Follow up on co… John C Klensin
- Re: [Manycouches] [admin-discuss] Follow up on co… Michael Richardson
- Re: [Manycouches] [admin-discuss] Follow up on co… Andrew Campling
- Re: [Manycouches] [admin-discuss] Follow up on co… Fred Baker
- Re: [Manycouches] [admin-discuss] Follow up on co… John C Klensin
- Re: [Manycouches] [admin-discuss] Follow up on co… Brian E Carpenter
- Re: [Manycouches] [admin-discuss] Follow up on co… Vittorio Bertola
- Re: [Manycouches] [admin-discuss] Follow up on co… Alexandre Petrescu
- Re: [Manycouches] [admin-discuss] Follow up on co… Alexandre Petrescu
- Re: [Manycouches] [admin-discuss] Follow up on co… Alexandre Petrescu
- Re: [Manycouches] [admin-discuss] Follow up on co… Alexandre Petrescu
- Re: [Manycouches] [admin-discuss] Follow up on co… Alexandre Petrescu