IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Wed, 16 February 2022 16:44 UTC

Return-Path: <bob.hinden@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 0869B3A1404 for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 08:44:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 hxFMe-5c6Phw for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 08:44:40 -0800 (PST)
Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B63BD3A1408 for <113attendees@ietf.org>; Wed, 16 Feb 2022 08:44:40 -0800 (PST)
Received: by mail-oi1-x22e.google.com with SMTP id q8so3031688oiw.7 for <113attendees@ietf.org>; Wed, 16 Feb 2022 08:44:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=e5ceX8TAwxQOasJ9CpebOmpfZjjc+6rb+IZ8O0GK/pE=; b=heSZ7gmI2bXxdQ23puF70nuaxfxrvYba/cS7cVe6YcQTtpRn0I4sTCvHMnAhxhQPjx qFlzSC1klrgjmkWljFmmob+byJxkFQYqmzAgxoLteFe/Q8bJmvnmtY+STiLMFDywlbaH 7HUsYizTp/R1LmNXJJ+xcyacERqyOX7HuBGCj+BwnbWhzzfart+w7yCjesVB/sdEN9yW a6RNVX/AeYd/4lZuN0NPAgR36e/zZjJZ4Og523IQK6R+bZxwaglAy/IbiENJhynyKBKe lp9xXMOpIbsrN4NQX5VL9pqdUVM+hRhx7PWYZVmmeGzXjssX/wFWe7VfiPsjC6zqjac0 QIRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=e5ceX8TAwxQOasJ9CpebOmpfZjjc+6rb+IZ8O0GK/pE=; b=u6sR/JfpOSVBCx3OMS83dRv/0RoRxZAEktlQM/rRxbwq7O51VcJkILNjkbWtmBqlhm W/Bh1JgFM1SKK5hN0cr0BUfKKgsDu0zFrFh0RliIQtdIOEOa7Pvv2ef79ysgPbp3MC1H gRP21K8V8ZAVTyPmm5k82MBsxgG0/e3G3DjdwHz7RlbleFyg8mpTm52VSWQjRvvfyGQS 06FNUk7e4aHmMuAJc+iQUSluv3jBaYujprnIbL8m40YgU2iaPYyEsCjwwZQdr88zUFps CtbTYsPI8pHdxEkIoVizQduSjAGQWoiY+iNU7WhHjJ/CZE5InGj44zxL9L0W3gpnwcpE sgCw==
X-Gm-Message-State: AOAM530JyAbw03OGdMziuHmnOro4pwCgmVsPCU+yi3YecqeR8tLsOZhd 1dZ+kxRdKX2tFbJnpjtw4Wk=
X-Google-Smtp-Source: ABdhPJzeJwE3kYvLX6kSlYr8VVxNYc339scwCpDOLTWh9OsxMLabwcRqJoP7RduGs6PiNoCKTZ39LA==
X-Received: by 2002:a05:6808:238e:b0:2d3:3006:2fc8 with SMTP id bp14-20020a056808238e00b002d330062fc8mr1144715oib.323.1645029878931; Wed, 16 Feb 2022 08:44:38 -0800 (PST)
Received: from smtpclient.apple ([2600:1700:4383:c05f:9409:1c9e:3f4c:dada]) by smtp.gmail.com with ESMTPSA id bk4sm16392495oib.24.2022.02.16.08.44.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Feb 2022 08:44:38 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_61D21EF4-8F69-4644-9DE0-A4B5DCE0F7B4"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Bob Hinden <bob.hinden@gmail.com>
X-Priority: 3
In-Reply-To: <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com>
Date: Wed, 16 Feb 2022 08:44:36 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, Greg Wood <ghwood@staff.ietf.org>, 113attendees@ietf.org
Message-Id: <E9A51103-58DB-47ED-A2D6-D83932150754@gmail.com>
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/zzZV6IrzJEjneVnkw_CqCJPb2qk>
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 16:44:54 -0000

Hi,

> On Feb 16, 2022, at 2:35 AM, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
> 
> 
> 
>> 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.

Further, a decision may be needed for each working group.  For example, if the chair(s) and responsible AD are not going to be in Vienna, it might be better to not hold a hybrid w.g. meeting and make it all virtual.

Bob


> 
> 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
> 
> --
> 113attendees mailing list
> 113attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/113attendees

v2.23.0 | Report a Bug | By Email