Re: [114attendees] [114all] Consultation on COVID management for IETF 115 London

Joel Halpern <jmh.direct@joelhalpern.com> Mon, 15 August 2022 22:44 UTC

Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: 114attendees@ietfa.amsl.com
Delivered-To: 114attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A5EC1526EB for <114attendees@ietfa.amsl.com>; Mon, 15 Aug 2022 15:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0TOOw2sKTB2 for <114attendees@ietfa.amsl.com>; Mon, 15 Aug 2022 15:44:07 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 726BCC14F74F for <114attendees@ietf.org>; Mon, 15 Aug 2022 15:44:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4M68Tg17ypz1pWC8; Mon, 15 Aug 2022 15:44:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1660603447; bh=w3juci7SCqu9FQtORa9Tx//xXgoxU1VOExicVkVZ5dU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Mr9yXdD4eKpvHzwJbUemKz1iWrcM5yCuol9aIDELWJSAXsGH9a4XVw2H4hL2Ci61n gMRDW+/AV1Dzg7LKq5VobpF3iRZuBxcIggVH0l/lYua0G9RsBhwbdIc0IK6Yc3vclK epvFHlT3KjCaNeYlUn24sBm157T4HJISQLB9/x74=
X-Quarantine-ID: <dpYf_riRcHGO>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.181] (unknown [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)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4M68Tf3CpZz1pNsk; Mon, 15 Aug 2022 15:44:06 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------Vh02wOp5VnCdau00nlPOZdJB"
Message-ID: <faa0f851-c269-a494-4570-d7a6cf947b94@joelhalpern.com>
Date: Mon, 15 Aug 2022 18:44:05 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Content-Language: en-US
To: Ted Lemon <mellon@fugue.com>
Cc: "114attendees@ietf.org" <114attendees@ietf.org>, Margaret Cullen <mrcullen42@gmail.com>
References: <4B348C11-79CE-4E7E-9DFD-B5CE79224767@ietf.org> <2F1594AF-4729-4908-918E-CD2151639E23@samuelsmith.org> <9c06d39e-0a03-916f-89e3-eff9ed2231bf@petit-huguenin.org> <CF6F11B2-6E3D-45FD-B520-29FE7DA52658@live555.com> <df828417-9229-4f67-93bf-9de9202e1950@petit-huguenin.org> <LO0P123MB660168369A86618248E627B5A9679@LO0P123MB6601.GBRP123.PROD.OUTLOOK.COM> <CAMOjQcFkuBWOGPCwP=UFbodA15R79COvncHw-nm1YmFFoL1N+w@mail.gmail.com> <6aa68882-60bb-4a7c-ad84-51c58f7bd78a@evequefou.be> <B53FD62C-6AFD-4048-823E-F723A14C207B@gmail.com> <9e5b5853-2f5b-e5ab-19da-562f8a099b7b@joelhalpern.com> <CAPt1N1kiuq6PnQUkKbqekdhoJ-s8EXiUAOyYKt3ekZ94vNokyg@mail.gmail.com>
From: Joel Halpern <jmh.direct@joelhalpern.com>
In-Reply-To: <CAPt1N1kiuq6PnQUkKbqekdhoJ-s8EXiUAOyYKt3ekZ94vNokyg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/114attendees/8fKyCflCYNya1kEPnQYvhR1BcV0>
Subject: Re: [114attendees] [114all] Consultation on COVID management for IETF 115 London
X-BeenThere: 114attendees@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mailing list for IETF 114 attendees <114attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/114attendees>, <mailto:114attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/114attendees/>
List-Post: <mailto:114attendees@ietf.org>
List-Help: <mailto:114attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/114attendees>, <mailto:114attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2022 22:44:11 -0000

I agree (and hope I made that clear in an earlier email) that the 
quesiton of how the policy affects the likelihood / willingness of 
people to attend is the key quesiton.

While not central, I thought Margaret's question might help some people, 
so I took a crack at answering it.

Yours,

Joel

On 8/15/2022 6:40 PM, Ted Lemon wrote:
> It’s also worth noting that when I am at home, I have a great deal of 
> control over the risks I take. When I’m at IETF, I’m at the mercy of 
> the IETF’s mitigation strategy. For some, that strategy will seem like 
> more than what they do at home. For others, perhaps less.
>
> A better question might be, how many people who would attend the 
> meeting were the policy different, as compared to how many attend it 
> with the current policy.
>
> If we think in person attendance is beneficial, this is really the 
> only question that matters. If we don’t think it’s important, we 
> should go back to online-only.
>
> On Mon, Aug 15, 2022 at 18:35 Joel Halpern <jmh@joelhalpern.com> wrote:
>
>     That comparison seems a reasonable question.
>
>     I am not a statistician or an epidemiologist, so I may have gotten
>     the comparatives wrong.
>
>     Looking at the data for Pennsylvania as reported by the New York
>     Times, they report for a week 25 cases per 100,000 people.  The
>     highest County reports 60 cases per 100,000.  Rounding our rate to
>     2.5 percent, and our attendance to 500 just to keep things simple,
>     our experience would be a rate of 500 cases per 100,000 people per
>     week.  So yes, attending the IETF meeting does seem to be related
>     to a significant increase in risk even with the rules we had in place.
>
>     If I have misunderstood the data, I hope  someone who knows more
>     will correct me.
>
>     Yours,
>
>     Joel
>
>     On 8/15/2022 3:39 PM, Margaret Cullen wrote:
>>
>>     Do we have any idea how the percentage of IETF attendees infected
>>     with COVID during the IETF week compares to the percentage who
>>     would have been infected if they stayed home?
>>
>>     Margaret
>>
>>
>>>     On Aug 12, 2022, at 6:07 PM, Mike Bishop <mbishop@evequefou.be>
>>>     wrote:
>>>
>>>     And this, in my opinion, is the primary goal. It is a useful
>>>     secondary goal to minimize excess exposure to CoVID among
>>>     participants relative to the exposure we would have had without
>>>     an IETF meeting. But the primary goal of the IETF's precautions
>>>     is to ensure enough attendees are willing to take the risk of
>>>     coming to ensure a successful meeting.
>>>
>>>     The recommendations as stated strike an excellent balance
>>>     between comforting the nervous, reducing transmission where
>>>     possible, and minimizing burden on attendees.
>>>
>>>     Sent from Nine <http://www.9folders.com/>
>>>     ------------------------------------------------------------------------
>>>     *From:* Eric Orth <ericorth=40google.com@dmarc.ietf.org>
>>>     *Sent:* Friday, August 12, 2022 2:25 PM
>>>     *To:* 114attendees@ietf.org
>>>     *Subject:* Re: [114attendees] [114all] Consultation on COVID
>>>     management for IETF 115 London
>>>
>>>     Scientifically beneficial or not (I'm not going to get into that
>>>     debate), the proposals Jay has outlined would go a long way
>>>     towards making me feel comfortable attending an international
>>>     conference, so I support those proposals.
>>>
>>>     On Fri, Aug 12, 2022 at 5:03 PM Yaron Sheffer
>>>     <yaronf.ietf@gmail.com> wrote:
>>>
>>>         +1 to Marc.
>>>
>>>         *From: *114attendees <114attendees-bounces@ietf.org> on
>>>         behalf of Marc Petit-Huguenin <marc@petit-huguenin.org>
>>>         *Date: *Saturday, 13 August 2022 at 0:00
>>>         *To: *Ross Finlayson <finlayson@live555.com>,
>>>         114attendees@ietf.org <114attendees@ietf.org>
>>>         *Subject: *Re: [114attendees] [114all] Consultation on COVID
>>>         management for IETF 115 London
>>>
>>>         We should do better than that. Except for the couple of
>>>         first days of IETF 114, the policy was stronger than what
>>>         was recommended locally and that's the reason why I will go
>>>         to London.  FTR I support everything Jay proposed.
>>>
>>>         On 8/12/22 13:34, Ross Finlayson wrote:
>>>         > I think that the IETF (and IETFers) should avoid straying
>>>         into areas outside their areas of expertise, and just follow
>>>         whatever policy is recommended by the locality where each
>>>         meeting is held.
>>>         >
>>>         >        Ross.
>>>         >
>>>
>>>         -- 
>>>         Marc Petit-Huguenin
>>>         Email: marc@petit-huguenin.org
>>>         Blog: https://marc.petit-huguenin.org
>>>         Profile: https://www.linkedin.com/in/petithug
>>>
>>>         -- 
>>>         114attendees mailing list
>>>         114attendees@ietf.org
>>>         https://www.ietf.org/mailman/listinfo/114attendees
>>>
>>>     -- 
>>>     114attendees mailing list
>>>     114attendees@ietf.org
>>>     https://www.ietf.org/mailman/listinfo/114attendees
>>
>>
>     -- 
>     114attendees mailing list
>     114attendees@ietf.org
>     https://www.ietf.org/mailman/listinfo/114attendees
>