IETF Logo Mail Archive

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

"Salz, Rich" <rsalz@akamai.com> Thu, 17 February 2022 18:10 UTC

Return-Path: <rsalz@akamai.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 9BE633A0EFA for <113attendees@ietfa.amsl.com>; Thu, 17 Feb 2022 10:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.675
X-Spam-Level:
X-Spam-Status: No, score=-7.675 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, 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=akamai.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 S5N722ZS2dDF for <113attendees@ietfa.amsl.com>; Thu, 17 Feb 2022 10:10:10 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 5DE223A0E54 for <113attendees@ietf.org>; Thu, 17 Feb 2022 10:09:17 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.1.2/8.16.1.2) with ESMTP id 21HEvuqS030939; Thu, 17 Feb 2022 18:09:03 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=bOvnR819h9oKCWsBUALuezGEAwfsCMJb8N+w6QSNC44=; b=PxTIUw9m34m/wlkjCT6ystMD47Jx0MRWGG5j47NKKXIdTBDSBG+omW8f7nEL5pxgjYJx q5/h5jYe4nPkvTwZsXpJRftZDvNB5yze+qrtdHiuKXB+rOrwSqKu1JvDeNaxoBwEtXqb NmpkKJLajOooURz2J4xGDMCL/8flDZBE8PUgXdW5NF5hqTlLeyAAJMKDhwMOSKwuu99V gZLg2Na8Q4QpFpkXzGUwIcVjiFO8J4p13ZE7V01P5Bw3hpaxl/PkxarCbFvVF5pm0FFh McGxMdlJnyXp4Av5oeAv6cakaIDmvZKfkGL4FEHU1tMtG4zsfbDKmbu/n/rCagwLOzMx WQ==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by m0050095.ppops.net-00190b01. (PPS) with ESMTPS id 3e92wjt65g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 17 Feb 2022 18:09:02 +0000
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 21HHnfdV003649; Thu, 17 Feb 2022 13:09:01 -0500
Received: from email.msg.corp.akamai.com ([172.27.91.23]) by prod-mail-ppoint6.akamai.com with ESMTP id 3e9js68pgq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 17 Feb 2022 13:09:01 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by usma1ex-dag4mb7.msg.corp.akamai.com (172.27.91.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.922.20; Thu, 17 Feb 2022 13:09:01 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.165.123) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Thu, 17 Feb 2022 12:09:00 -0600
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.028; Thu, 17 Feb 2022 12:08:59 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Jim Reid <jim@rfc1035.com>, Jan Zorz <jan@go6.si>
CC: "113attendees@ietf.org" <113attendees@ietf.org>
Thread-Topic: [113attendees] Predicting go/no go dates for IETF113
Thread-Index: AQHYJCkDTe91lNG0oUaAhSeRsD6xa6yYG1CA
Date: Thu, 17 Feb 2022 18:08:59 +0000
Message-ID: <A233633A-2677-4498-8632-6F670850EB84@akamai.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>
In-Reply-To: <8F1E4D76-18E1-4621-B70F-0FD290A32EF3@rfc1035.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.58.22020202
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B2F1601A996B0144803F3739060026F2@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-02-17_06:2022-02-17, 2022-02-17 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 suspectscore=0 malwarescore=0 mlxlogscore=745 mlxscore=0 phishscore=0 adultscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2201110000 definitions=main-2202170081
X-Proofpoint-GUID: E0fzDRhlLD1mc4eWPS1hGcQQq7yhw46c
X-Proofpoint-ORIG-GUID: E0fzDRhlLD1mc4eWPS1hGcQQq7yhw46c
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.816,Hydra:6.0.425,FMLib:17.11.62.513 definitions=2022-02-17_06,2022-02-17_01,2021-12-02_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 spamscore=0 lowpriorityscore=0 mlxscore=0 phishscore=0 adultscore=0 mlxlogscore=737 bulkscore=0 priorityscore=1501 clxscore=1011 suspectscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2201110000 definitions=main-2202170084
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/dOVKQTLbYrm9H1LPZU5-6nc3hCI>
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:10:20 -0000

>    To be less glib, nobody can say for certainty when or if the physical meeting will get cancelled. Health and travel regulations could change at any moment. Or a new variant of COVID19 erupts out of nowhere, etc, etc. Even after some hypothetical go/no go date,

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.

v2.23.0 | Report a Bug | By Email