Re: [Manycouches] Follow up on consultation on planning for IETF 111
Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 09 April 2021 12:25 UTC
Return-Path: <alexandre.petrescu@gmail.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 B47323A1F6D; Fri, 9 Apr 2021 05:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.648
X-Spam-Level:
X-Spam-Status: No, score=0.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 Ud5i_QF85tn6; Fri, 9 Apr 2021 05:25:07 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEE13A1F6C; Fri, 9 Apr 2021 05:25:06 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 139CP3ck021055; Fri, 9 Apr 2021 14:25:03 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 64697206ED8; Fri, 9 Apr 2021 14:25:03 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 54C6B203F64; Fri, 9 Apr 2021 14:25:03 +0200 (CEST)
Received: from [10.14.11.68] ([10.14.11.68]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 139CP2qQ016526; Fri, 9 Apr 2021 14:25:03 +0200
To: Jay Daley <jay@ietf.org>, manycouches@ietf.org
Cc: admin-discuss@ietf.org
References: <3431E359-7CDE-43AE-9284-56A9C0AC3A1A@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d4eaa5ce-083f-7558-28a9-fc0df7d817a5@gmail.com>
Date: Fri, 09 Apr 2021 14:25:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.1
MIME-Version: 1.0
In-Reply-To: <3431E359-7CDE-43AE-9284-56A9C0AC3A1A@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/E3ZbSjscuyWi4HrP6IVw0GA4NN4>
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: Fri, 09 Apr 2021 12:25:12 -0000
Hi, Le 06/04/2021 à 23:43, Jay Daley a écrit : > The consultation on proposals regarding planning for IETF 111 > finished on 2 April. Several points were raised and are paraphrased > and addressed as follows: > > a. Consider what other events are taking place *globally* not > locally This feedback is rejected as inappropriate given the highly > local nature of restrictions, such as travel bans, face mask > regulations and so on. > > b. Make the criteria more specific because people might interpret > them differently This hasn’t been a problem so far and no evidence is > provided that it will, besides which the assessment document is not a > consensus opinion. > > c. Include X in this criteria In every case where this was raised, > the language is general enough to include X and intended to include X > and it would be unwieldy to enumerate every aspect of the criteria at > the same level as X. > > d. Consider hybrid meetings This work has now started, but > potentially targeting IETF 112 not IETF 111 given the work required > > e. Delay the decision to the 10 weeks before the meeting not 14 > weeks After speaking to the OP they have withdrawn this suggestion on > the basis that is looks unlikely anything substantial will change in > the intervening four weeks. > > > On this basis I intend to stick with the proposed timetable and > process: > > 1. Assessment Criteria We will use the same criteria [1] for > assessing whether to go ahead with an in-person IETF 111 meeting or > switch to an online meeting as used for IETF 109. These criteria > were previously consulted on, amended as a result of the > consultation, and worked well when used for IETF 109 [2]. > > 2. Fee structure We will use the same fee structure as used for IETF > 110 [3] including unlimited fee waivers. > > 3. Decision timetable We will use the following assessment > timetable: > > 05 Mar 2021 This consultation opens. > > 02 Apr 2021 Consultation closes. > > 09 Apr 2021 Response to consultation communicated and assessment > begins using the final criteria. > > 16 Apr 2021 Decision made and communicated. > > 03 May 2021 Registration opens. > > 26 Jul 2021 IETF 111 begins. > > > Please let me know if you think I have missed anything or if you > otherwise disagree. I agree with the Assessment Criteria, Fee structure and happy to see the decision timetable. I think it is followed and I feel reassured a plan is followed. My comment is late on-purpose such that to not deviate the discussion. But I would like to say something here. There are hybrid meeting considerations - ok. The vaccination and sanitary seem to advance on a positive path towards returning to a more 'normal' - ok. However, I do not think it is that simple. When I was still subscribed to the IETF list there was a sort of a charter proposal about a possibility of a somehow different worldview, that would witness many fundamental changes. I think I will need to look at that again. Because some times, and recently more often, I think that - other than the hybrid meetings topic - the very core of the reason of why meeting is being shaken. That comment has many ramifications. Is it worth polluting the air for something that could be decided online? Is one disturbing the world less or more if one is using a PC or otherwise a plane seat to meet? Can trust be maintained and further built, if remote? How many people can actually constitute a 'core' that needs to meet about the Internet during even the most difficult times? And, above all, is the Internet itself a good thing or a less good thing in this picture? When pondering our ways forward these are almost mandatory considerations, IMHO. Some might call it Ethics and leave it to others to address. It is a possibility. Alex > > Jay > > [1] > https://www.ietf.org/how/meetings/109/assessment-framework-person-vs-online-ietf-109-meeting/ > > [2] https://mailarchive.ietf.org/arch/msg/ietf-announce/7GHV8JuZuNgYjv-Dt9wrk_CN5BE/ > [3] > https://mailarchive.ietf.org/arch/msg/ietf-announce/ZU6cYhBTdxD63Ki2c4hUSsVfkCw/ >
- [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