Re: [Manycouches] [admin-discuss] Follow up on consultation on planning for IETF 111
John C Klensin <john-ietf@jck.com> Fri, 09 April 2021 20:35 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 13A293A1006 for <manycouches@ietfa.amsl.com>; Fri, 9 Apr 2021 13:35:13 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 j5BnhPkRvwQC for <manycouches@ietfa.amsl.com>; Fri, 9 Apr 2021 13:35:09 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 E30A13A0FD8 for <manycouches@ietf.org>; Fri, 9 Apr 2021 13:35:08 -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 1lUxqN-000B6R-7l; Fri, 09 Apr 2021 16:35:07 -0400
Date: Fri, 09 Apr 2021 16:35:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, shmoo <manycouches@ietf.org>
Message-ID: <9F0A812EC6497AECE61626C0@PSB>
In-Reply-To: <3bf17293-5a7d-78a2-b8cf-1b32de9b879c@gmail.com>
References: <3431E359-7CDE-43AE-9284-56A9C0AC3A1A@ietf.org> <d4eaa5ce-083f-7558-28a9-fc0df7d817a5@gmail.com> <80C5BA10-4D11-4B48-95F4-918ECC01579A@cable.comcast.com> <3bf17293-5a7d-78a2-b8cf-1b32de9b879c@gmail.com>
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/35-ZwgAZQBlG2GwFf721j6V_uMg>
Subject: Re: [Manycouches] [admin-discuss] 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: Fri, 09 Apr 2021 20:35:19 -0000
--On Saturday, April 10, 2021 08:21 +1200 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > I have fairly violent feelings about purchasing carbon credits > as virtue signalling, but rather than go there, let me ask > whether discussing a strategic decision to reduce the > (post-pandemic) number of meetings per year is within this > WG's charter. Skipping the carbon credit question for now, I've been having much the same reaction, especially as we watch the number of interim meetings continue to grow. So, let me pose a slightly different question: Assume that starting with IETF 11X (X >= 1) we decide it is post-pandemic and go back to a "normal" meeting schedule. Should the IESG and the broader community then return to pushing back on many between-IETF-meeting interims and encourage a return to mailing lists, those IETF meetings, and using interims _very_ sparingly? Or, if many interims are now part of how we do business that will not change post-pandemic, exactly what do we think the full IETF meetings accomplish and can that be accomplished (and participation broadened) by having fewer of them. If the answer is to reconsider how many IETF meetings we need a year, does that optimally mean just fewer all-IETF meetings or a permanent mix of nominally in-person and all-remote meetings. If discussing that is not within the charter of this WG, where is the appropriate place? 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