IETF Logo Mail Archive

Re: [113attendees] Predicting go/no go dates for IETF113

Jim Reid <jim@rfc1035.com> Thu, 17 February 2022 18:20 UTC

Return-Path: <jim@rfc1035.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 DC2DE3A0E5E for <113attendees@ietfa.amsl.com>; Thu, 17 Feb 2022 10:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 CnyxdPUStfsJ for <113attendees@ietfa.amsl.com>; Thu, 17 Feb 2022 10:20:54 -0800 (PST)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A31D3A0E60 for <113attendees@ietf.org>; Thu, 17 Feb 2022 10:20:53 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id C6F862421481; Thu, 17 Feb 2022 18:20:51 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <A233633A-2677-4498-8632-6F670850EB84@akamai.com>
Date: Thu, 17 Feb 2022 18:20:50 +0000
Cc: "113attendees@ietf.org" <113attendees@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <56AF0FE5-1422-488A-A7F3-AF9F56E657D7@rfc1035.com>
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com> <07d87027-8162-b421-f157-6fff580d0b8b@go6.si> <8F1E4D76-18E1-4621-B70F-0FD290A32EF3@rfc1035.com> <A233633A-2677-4498-8632-6F670850EB84@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/xtGVOKQ7dgQ8hMjFUAxVhRJyMcw>
Subject: Re: [113attendees] Predicting go/no go dates for IETF113
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: Thu, 17 Feb 2022 18:20:56 -0000


> On 17 Feb 2022, at 18:08, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> 
> Yes they can.  As stated when the meeting was first announced, the IESG can cancel if they decide attendance is insufficient, and Jay mentioned that our insurance will be sufficient.

While this is true, that wasn’t the orginal question:

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

You answered the first one (about an IETF-decided call off). I answered the second. Which was about someone else making the decision for the IETF leadership/secretariat.

v2.23.0 | Report a Bug | By Email