IETF Logo Mail Archive

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

Vittorio Bertola <vittorio.bertola@open-xchange.com> Wed, 16 February 2022 10:35 UTC

Return-Path: <vittorio.bertola@open-xchange.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 1F6603A0E12 for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 02:35:44 -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=open-xchange.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 WcgUAjKFkfqO for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 02:35:39 -0800 (PST)
Received: from mx4.open-xchange.com (mx4.open-xchange.com [87.191.57.184]) (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 98B293A0E14 for <113attendees@ietf.org>; Wed, 16 Feb 2022 02:35:39 -0800 (PST)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPSA id B25F66A0E1; Wed, 16 Feb 2022 11:35:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1645007735; bh=Vph7X+5LH6oygp2GgOh7jRqZNOw0D6XDFtxU5S2a1tw=; h=Date:From:To:In-Reply-To:References:Subject:From; b=BNycWrgr8xw+bjt6OTBURC2MFzeQCC/C3XkEf4h8rjJ6DoIf5I+3DyjbjXnGR3Eny rv/DkarsB7x/lyH8eWSsCsEAhB+V6qXQmFoHIDbUUHAcNj9Vve8OK9DCT+ipjuxKnD mWHMORv5Mp6K4QKu/MfxZEtgyIgNwpKUPnhcRisWOuCBc0PZ86btanyDVY4ClWBDAh k5t+PtmDBKIqmbWo9qwSJfJyiO7MDOt/FcCw/RYAfm/TXjduQa9ofosat3pcROzvkQ u6ZE+JlSNEdC5kZfyBpwVm3gk21JkwUlSJfjnxfTsPTF7Mw/LiGYRMmWRC3ypr8w5W w/Zn8MrdY8GNQ==
Received: from appsuite-gw2.open-xchange.com ([10.20.28.82]) by imap.open-xchange.com with ESMTPSA id AXLsKXfTDGJcDgAA3c6Kzw:1 (envelope-from <vittorio.bertola@open-xchange.com>); Wed, 16 Feb 2022 11:35:35 +0100
Date: Wed, 16 Feb 2022 11:35:35 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Greg Wood <ghwood@staff.ietf.org>, 113attendees@ietf.org
Message-ID: <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com>
In-Reply-To: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org>
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev9
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/A0FbXviCvIvJQGcSG7DYCyO-sXs>
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 10:35:45 -0000


> 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 - 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.

Is there a final "go/no go" date for this latter type of meeting cancellation? (perhaps in the past already?)

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?

Thanks,

-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy

v2.23.0 | Report a Bug | By Email