Re: [113attendees] IETF 113 Update: 2022-02-10
Michael Richardson <mcr+ietf@sandelman.ca> Fri, 18 February 2022 19:49 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: 113attendees@ietfa.amsl.com
Delivered-To: 113attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDCE3A1420 for <113attendees@ietfa.amsl.com>; Fri, 18 Feb 2022 11:49:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 XX3WiDa71KyC for <113attendees@ietfa.amsl.com>; Fri, 18 Feb 2022 11:49:40 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D91DB3A13F5 for <113attendees@ietf.org>; Fri, 18 Feb 2022 11:49:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id ACB4038A73; Fri, 18 Feb 2022 14:57:53 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dFQLQk_C8d8k; Fri, 18 Feb 2022 14:57:49 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A3B7638A6C; Fri, 18 Feb 2022 14:57:49 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1645214269; bh=fr83KDXicDfsGslk7UwXKgOZ6UyWaQBzmUn1SJBmzJg=; h=From:To:Subject:In-Reply-To:References:Date:From; b=9wgzYk1MWI/LR5RW+BQ6nXaDLEZ83Q74bLmsnvTyuQC3DO+K3hhp//+j6T3NKmENz w4/hcQolEZl4MpUDGCJq4SRQMaaAl/pYjSowqi9enMTkE3yAs8KWWD+2rdS4LmKQ+P GISzGYc3XNv8cKL5TyNydQZd/kcuz8LuLfMOiZQmtdf04ev4/sDbgl6WPXAcS9eQbD pTRgF6/a6GIb2f24D6xJD9iMUIa/q1kJE1G1g6zSyl+GoSqDFMkDBL/Ad+1LBfrl4l YsnwktvHWNIl8GzBaBF2bZjGO50zsHfYGsIJaWNu3+VDZXL1CkHcsJpDcsZzvfv3Mi 9L6DHqy7VDWbw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A88C9527; Fri, 18 Feb 2022 14:49:33 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Scheffenegger, Richard" <rs.ietf@gmx.at>, 113attendees@ietf.org
In-Reply-To: <c26150cd-f866-c6d9-1042-9ecebeca56b3@gmx.at>
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com> <07d87027-8162-b421-f157-6fff580d0b8b@go6.si> <26EB1DEC-9132-433B-9F62-F7ECD32C92BE@ietf.org> <41FACD64-7B36-4842-AF45-308AD35276D6@tzi.org> <c26150cd-f866-c6d9-1042-9ecebeca56b3@gmx.at>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 18 Feb 2022 14:49:33 -0500
Message-ID: <27742.1645213773@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/VAfpXwZeuu50RFTCQyCRESkMZjA>
Subject: Re: [113attendees] IETF 113 Update: 2022-02-10
X-BeenThere: 113attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 113 attendees <113attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/113attendees>, <mailto:113attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/113attendees/>
List-Post: <mailto:113attendees@ietf.org>
List-Help: <mailto:113attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/113attendees>, <mailto:113attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2022 19:49:56 -0000
Scheffenegger, Richard <rs.ietf@gmx.at> wrote: > Please bookmark this page, and consult when your personal go/no-go > decision point comes close. > https://www.sozialministerium.at/Informationen-zum-Coronavirus/COVID-Prognose-Konsortium-2022.html Thank you. Google translated for me. I looked at the graphs, and I see a yellow label: "Now casting" Do you understand what this means? > (Free PCR testing will still be available, while the IETF is running. > But political debates have started if this is reasonable to continue > when the healthcare system starts to recover and return back to normal > levels - with an nudge for those who believed that testing is just as > good as getting vaccinated, to finally get their shots). The Austrian level of testing is leaps above what has been available in Ottawa. I wish that the debate here was between whether to continue testing for 2 months or 4 months, rather than whether the entire thing was a hoax. In Ottawa, we have: https://613covid.ca/wastewater/ where we have some researchers from OttawaU. An irony is that we have really only a single wastewater treatment plant, it's regularly overloaded (dumping raw sewage!). Many in the community have over decades criticized having a single non-redundant facility, and pumping waste water 60km across the region. We've had significant floods caused by failures of the pumps. But, having it all in one place has made it easy to look for the COVID signal. -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- [113attendees] IETF 113 Update: 2022-02-10 Greg Wood
- Re: [113attendees] IETF 113 Update: 2022-02-10 Michael Richardson
- Re: [113attendees] IETF 113 Update: 2022-02-10 Dr Eberhard W Lisse
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jeffrey (Zhaohui) Zhang
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Vittorio Bertola
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexander Mayrhofer
- [113attendees] Breaking news: IETF 113 will be af… Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Bob Hinden
- Re: [113attendees] IETF 113 Update: 2022-02-10 Toerless Eckert
- Re: [113attendees] IETF 113 Update: 2022-02-10 Andrew Campling
- Re: [113attendees] IETF 113 Update: 2022-02-10 Joel M. Halpern
- Re: [113attendees] IETF 113 Update: 2022-02-10 Eric Vyncke (evyncke)
- Re: [113attendees] IETF 113 Update: 2022-02-10 Warren Kumari
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexander Mayrhofer
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jan Zorz - Go6
- [113attendees] Predicting go/no go dates for IETF… Jim Reid
- Re: [113attendees] Predicting go/no go dates for … Salz, Rich
- Re: [113attendees] Predicting go/no go dates for … Jan Zorz - Go6
- Re: [113attendees] Predicting go/no go dates for … Jim Reid
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jay Daley
- Re: [113attendees] IETF 113 Update: 2022-02-10 Carsten Bormann
- Re: [113attendees] IETF 113 Update: 2022-02-10 Marc Petit-Huguenin
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jay Daley
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Dr Eberhard W Lisse
- Re: [113attendees] IETF 113 Update: 2022-02-10 Vittorio Bertola
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 John C Klensin
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Michael Richardson
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jan Zorz - Go6
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Eberhard W Lisse
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jan Zorz - Go6
- Re: [113attendees] IETF 113 Update: 2022-02-10 Petr Špaček
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Petr Špaček
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre PETRESCU
- Re: [113attendees] Breaking news: IETF 113 will b… Alexandre Petrescu
- Re: [113attendees] Breaking news: IETF 113 will b… Alexander Mayrhofer
- Re: [113attendees] Breaking news: IETF 113 will b… Marc Petit-Huguenin
- Re: [113attendees] Breaking news: IETF 113 will b… Greg Wood
- Re: [113attendees] Breaking news: IETF 113 will b… Rohan Mahy
- Re: [113attendees] Breaking news: IETF 113 will b… Marc Petit-Huguenin
- Re: [113attendees] Breaking news: IETF 113 will b… Eric Vyncke (evyncke)
- Re: [113attendees] Breaking news: IETF 113 will b… Dr Eberhard W Lisse
- Re: [113attendees] Breaking news: IETF 113 will b… Corine de Kater
- Re: [113attendees] Breaking news: IETF 113 will b… Marc Petit-Huguenin
- Re: [113attendees] Breaking news: IETF 113 will b… Scheffenegger, Richard
- Re: [113attendees] Breaking news: IETF 113 will b… Alexandre Petrescu
- Re: [113attendees] Breaking news: IETF 113 will b… Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu