Re: [112attendees] Plenary last week -

Joel Halpern Direct <jmh.direct@joelhalpern.com> Wed, 10 November 2021 15:12 UTC

Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: 112attendees@ietfa.amsl.com
Delivered-To: 112attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0826E3A10DA for <112attendees@ietfa.amsl.com>; Wed, 10 Nov 2021 07:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.43
X-Spam-Level:
X-Spam-Status: No, score=-5.43 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-3.33, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 WB_DFDd6AnoJ for <112attendees@ietfa.amsl.com>; Wed, 10 Nov 2021 07:12:20 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 985FA3A10DB for <112attendees@ietf.org>; Wed, 10 Nov 2021 07:12:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4Hq7cg4JTrz6G8wf; Wed, 10 Nov 2021 07:12:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1636557139; bh=lBTitmjsLxDTVwu2VuJnu5AhrnxN3X4B6b0noZ2wtg8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=U1M5gHyjTGm8mwM1TjrjMQAiqZjprWOv7jD8+NnkDaWI2n1NN2ILN/dfR5cWVTZ0n WRyPR1iRkTi9UzPU2B3iKTKZ9mzXguMmJYQMQsPEdc0Quga9BOXfnybtt8cGNLnuC5 Err/FLsaBj7eyrzM7UyuyVwNpE4i2JFyNChoH9Jw=
X-Quarantine-ID: <zfm-1VotPtzZ>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4Hq7cg0Zkqz6G7lk; Wed, 10 Nov 2021 07:12:18 -0800 (PST)
Message-ID: <be661f7d-8cad-beef-ac02-6b8475461866@joelhalpern.com>
Date: Wed, 10 Nov 2021 10:12:18 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Content-Language: en-US
To: Alexandre PETRESCU <alexandre.petrescu@cea.fr>, 112attendees@ietf.org
References: <d1fc4b13-89a7-3096-7b9a-6d62997a9b68@cea.fr> <9360c78d-04a2-bb8e-5431-92f8dcd12274@labs.htt-consult.com> <0d62c15a-cc34-161e-53d3-c30314094bed@cea.fr> <5DC79F14-6C21-44B8-9C24-1F62A3AC4685@ericsson.com> <14eb9214-3e2c-b4c4-c9a0-83388c50570f@cea.fr> <c7f8aab3-2366-7f56-f7dd-258943f9b2b5@isc.org> <LO3P265MB2092F4F4FEB4A2EAF03EC793C2939@LO3P265MB2092.GBRP265.PROD.OUTLOOK.COM> <a47511dd-be42-2036-6925-ede98a89baba@cea.fr> <98d449fe-af9f-a9db-9c3e-d78a5c3cff54@joelhalpern.com> <4b22c574-6ada-37cf-d705-5cab797e48ec@cea.fr>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
In-Reply-To: <4b22c574-6ada-37cf-d705-5cab797e48ec@cea.fr>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/112attendees/DqxYRHmORHSTeyce-Bz4OHP1wvg>
Subject: Re: [112attendees] Plenary last week -
X-BeenThere: 112attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 112 attendees <112attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/112attendees>, <mailto:112attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/112attendees/>
List-Post: <mailto:112attendees@ietf.org>
List-Help: <mailto:112attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/112attendees>, <mailto:112attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2021 15:12:25 -0000

I would be quite distressed if the IETF leadership described the regimen 
you ask for below ("commitment to realize the inhouse-designed 
protection means, test before, test after and publicize the results.") 
as any kind of guarantee.  And knowing the folks involved, I would be 
amazed if they used such a word to describe it.

Maybe you are using the word "guarantee" differently?

Yours,
Joel

On 11/10/2021 10:04 AM, Alexandre PETRESCU wrote:
> Le 10/11/2021 à 15:37, Joel M. Halpern a écrit :
>> I find your phrasing misleading. No one can offer a guarantee of 
>> non-spread.  Ever.  We do not guarantee you will not catch the flu
>> at an IETF meeting.  Or any other communicable disease.
> 
> Yes.  But I would not simply equate covid to any kind of other
> communicable disease.
> 
> First, covid is deadly much more than (in)flu(enza), for example.
> 
> Second, covid is transmitted by simply being next to the other - breath,
> as compared to other more complex transmissions like touching, spit,
> blood exchange, reuse common objects, moustique bite, or so.
> 
> I sometimes fear that whenever one is behind some person in the street
> and feels the smell of that person, that could be a risk of
> transmission.  I smell that even while wearing a fully-qualified mask.
> 
> Third, no other illness has previously been communicated that far that 
> fast.
> 
>> Even when (I hope it is a "when") this pandemic has finally faded to 
>> low levels, there will be no guarantees.
> 
> Maybe it is a 'when' and it would be good.
> 
> But if it is not a 'when', then what would be another way (other than
> meetings with guarantees) out of it?
> 
> Live with it?  Does one fully appreciates what it means to 'live with
> it' or does one tell _others_ to 'live with it'?
> 
> Otherwise,
> 
> There can be guarantees for in-person meetings, in a best effort kind of
> way.
> 
> One would run a meeting with inhouse-designed protection means, test PCR
> the input, and test PCR the output.  If the two are equal then there is
> a 'guarantee'.
> 
> A 'claimed guarantee' would be a statement that there is a commitment to
> realize the inhouse-designed protection means, test before, test after
> and publicize the results.
> 
> The 'proven guarantee' would be only when the publicized results were
> both 0.
> 
> Wouldnt one think that could qualify as 'guarantee', 'claimed guarantee'
> and 'proven guarantee' respectively?
> 
> Alex
> 
>>
>>
>> Yours, Joel
>>
>> On 11/10/2021 9:26 AM, Alexandre PETRESCU wrote:
>>> Le 10/11/2021 à 13:56, Andrew Campling a écrit :
>>>> On 10. 11. 21 12:45, Petr Špacek wrote:
>>>>
>>>>> As a second data point (obviously anecdotal): I'm heads-down
>>>>> in DNS stuff and don't follow internal IETF policies or shmoo 
>>>>> discussions, and still I had no problem finding out about Plenary 
>>>>> being a week earlier. In fact I remember seeing the information at 
>>>>> least three times - despite me ignoring plenary on purpose:
>>>>
>>>> I also saw multiple notifications of the change in the
>>>> scheduling of the plenary plus explanations of the reasons behind
>>>> the experiment. It seemed pretty well publicised to me and in
>>>> good time to allow for diary adjustments etc, noting that
>>>> attendance would not be possible for everyone and that (I hope)
>>>> the post-meeting review will reflect on the pros and cons of the 
>>>> approach.
>>>>
>>>> Separately, I trust that the plenary will take place during the week 
>>>> of the main meeting in IETF 113, assuming that there is an in-person 
>>>> element for this meeting.
>>>
>>> I think that, unless the organizers consider offering guarantees
>>> of non-spread, there could be an important point to make that we
>>> want first and foremost to not spread and hence not to meet.
>>>
>>> Of course, we could also want to meet even if we help the spread, but 
>>> in an advantageous ratio.
>>>
>>> We might also think that it is those who invite that must make
>>> sure there is no spread, or we might think that it is the 
>>> responsibility of those who come to ensure that.
>>>
>>> (this 'no spread' aspect comes to my mind personally after having 
>>> some ups and downs between optimism and pesimism about vaccines, 
>>> treatments, tests, mechanical, biological, electronic solutions)
>>>
>>> Alex
>>>
>>>>
>>>>
>>>> Andrew
>>>>
>>>