Re: [113attendees] IETF 113 Update: 2022-02-10

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 16 February 2022 11:47 UTC

Return-Path: <alexandre.petrescu@gmail.com>
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 EEF9D3A0CA8 for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 03:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level:
X-Spam-Status: No, score=-2.345 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.714, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, 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 QGdc0tAvjV4o for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 03:47:42 -0800 (PST)
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 877EC3A0CA6 for <113attendees@ietf.org>; Wed, 16 Feb 2022 03:47:42 -0800 (PST)
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 21GBldJw013589 for <113attendees@ietf.org>; Wed, 16 Feb 2022 12:47:39 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B95EC207CBD for <113attendees@ietf.org>; Wed, 16 Feb 2022 12:47:39 +0100 (CET)
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 AF8BE20295F for <113attendees@ietf.org>; Wed, 16 Feb 2022 12:47:39 +0100 (CET)
Received: from [10.8.32.130] (is245935.intra.cea.fr [10.8.32.130]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 21GBldDB008804 for <113attendees@ietf.org>; Wed, 16 Feb 2022 12:47:39 +0100
Message-ID: <2776a36d-ea56-2c74-6609-0ab116a3d723@gmail.com>
Date: Wed, 16 Feb 2022 12:47:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0
Content-Language: fr
To: 113attendees@ietf.org
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com> <988664ed-2cad-1b36-b6cf-b438bb8064d9@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <988664ed-2cad-1b36-b6cf-b438bb8064d9@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/Q6sfDhXknxVJlphnS53P6WkloKg>
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: Wed, 16 Feb 2022 11:47:47 -0000

also, one additional point.

Despite an innocent effort to try to make a sense of it, there are many 
things that clearly dont make sense.  For example, in Denmark the waves 
are all on a rise yet the restrictions are eased.  There are reasons 
that escape me.

That means that indeed many things can change any time, and it is not 
easy to predict.

Alex

Le 16/02/2022 à 12:03, Alexandre Petrescu a écrit :
> 
> 
> Le 16/02/2022 à 11:35, Vittorio Bertola a écrit :
>>
>>
>>> Il 11/02/2022 00:31 Greg Wood <ghwood@staff.ietf.org> ha scritto:
>>>
>>> As always, questions about IETF 113 are welcome at support@ietf.org.
>>
>> I have a question, I could not find the answer and I think it could 
>> affect others as well.
>>
>> The IETF 113 FAQs mention that the IETF, at a certain point in time, 
>> could "determine that 113 can no longer be held as a hybrid meeting 
>> with participants onsite in Vienna" and switch to a fully virtual 
>> meeting.
>>
>> This could happen due to new restrictions being imposed by the 
>> Austrian government on travel or on events in general, and this is 
>> unpredictable
> 
> The more we approach the meeting date, the more predictable are the
> covid-related matters.
> 
> The shapes of waves follow a certain tendency.  The wave in Austria
> might be at a mid low at end of March.  But it is important to know the
> waves of each visitor's country, not just Austria.
> 
> Covid measures and restrictions (vaccine mandates, QR codes, PCR
> mandates and more): the direction of covid measures countries take
> follow certain tendencies.  Denmark, UK, Croatia ease covid restrictions
> including QR codes; Italy seems to strengthen the QR codes use.  China,
> HK, Taiwan, SKorea maintain or strengthen restrictions; Australia, NZ
> are newly opening.  Canada eases restrictions.
> 
> France is on the direction of easying the restrictions.
> 
> Austria seems to continue keeping restrictions in place, but it might be
> they open more by end of March.  It is not known.
> 
> There are less chances that Austria strengthens restrictions by end of
> March, and more chances that Austria eases restrictions by end of March.
> 
> It is possible that by end of March the mask mandates and daily PCR
> testing mandates in Vienna are removed.  It is also possible that they
> are kept.
> 
>> - it could happen two days before the meeting and no one could do
>> anything about it.
>>
>> However, in theory this could also happen because the IETF (LLC? 
>> staff?) decides that something is going wrong with the process; for 
>> example, not enough onsite registrations, or widespread unavailability 
>> of chairs for working group meetings, or whatever.
> 
> I agree, that is also a possibility.
> 
>> Is there a final "go/no go" date for this latter type of meeting 
>> cancellation? (perhaps in the past already?)
> 
> I wonder the same?
> 
>> I mean, is there a date after which I can be sure that unless some 
>> real "force majeure" event happens the meeting will be held in person, 
>> and make my bookings with a bit more certainty?
> 
> I agree with the question.  It would be expected to have such a date.
> It would be advantageous to have such a date.
> 
> For my part, I do not condition my participation to such a date, because
> I largely already made up my mind.
> 
> Alex
> 
>>
>> Thanks,
>>
>