IETF Logo Mail Archive

Re: [Manycouches] Follow up on consultation on IETF 112 and COVID-related restrictions

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 03 August 2021 18:01 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 7E2CA3A2BE3 for <manycouches@ietfa.amsl.com>; Tue, 3 Aug 2021 11:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 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.001, RCVD_IN_MSPIKE_WL=0.001, 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 DXK3TQhEiORZ for <manycouches@ietfa.amsl.com>; Tue, 3 Aug 2021 11:01:08 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 A64173A2BE6 for <manycouches@ietf.org>; Tue, 3 Aug 2021 11:01:08 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 173I15Pq036628 for <manycouches@ietf.org>; Tue, 3 Aug 2021 20:01:05 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9AEA920522D for <manycouches@ietf.org>; Tue, 3 Aug 2021 20:01:05 +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 91876205169 for <manycouches@ietf.org>; Tue, 3 Aug 2021 20:01:05 +0200 (CEST)
Received: from [10.14.0.106] ([10.14.0.106]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 173I15eK026044 for <manycouches@ietf.org>; Tue, 3 Aug 2021 20:01:05 +0200
To: manycouches@ietf.org
References: <0AD65B7F-38BB-4AD6-B11B-226E01EDA1BC@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ed1e6748-391a-3c1b-5b08-30aa0612c683@gmail.com>
Date: Tue, 03 Aug 2021 20:01:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <0AD65B7F-38BB-4AD6-B11B-226E01EDA1BC@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/W-cFlkltqHJNRZUAI7pbhLegqw8>
Subject: Re: [Manycouches] Follow up on consultation on IETF 112 and COVID-related restrictions
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: Tue, 03 Aug 2021 18:01:15 -0000

Le 03/08/2021 à 01:49, IETF Executive Director a écrit :
[...]

> - the IETF should specify the least invasive testing method.  The IETF will not be doing any testing itself and any requirements will be based solely on local laws/regulations.

I must say that I go through a very pessimistic period about this.

PErsonal experience shows that the least invasive method is least 
reliable.  For best reliability one should use the most invasive 
method.  The worst happens when the least invasiveness (less hurt) means 
most wrong follow-up decisions.

This is in itself is a strong reason of pessimism.  I think this problem 
can not be fixed.

Alex

>
>
> Work has begun on assessing if IETF 112 Madrid can go ahead as an in-person meeting with an announcement due next Monday 9 August or earlier.
>
>
> [1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/R-1NLlYaYrZ7ldFZ0oPQWCFKfZg/
> [2]  https://datatracker.ietf.org/doc/draft-ietf-shmoo-cancel-meeting/
>

v2.23.0 | Report a Bug | By Email