IETF Logo Mail Archive

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

Jan Zorz - Go6 <jan@go6.si> Thu, 17 February 2022 17:34 UTC

Return-Path: <jan@go6.si>
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 9F4293A0AFF for <113attendees@ietfa.amsl.com>; Thu, 17 Feb 2022 09:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.813
X-Spam-Level:
X-Spam-Status: No, score=-2.813 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, NICE_REPLY_A=-0.714, 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=go6.si header.b=S0I5R/AN; dkim=pass (1024-bit key) header.d=go6.si header.b=a2NnuXZn
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 J2wuWiW-0Exa for <113attendees@ietfa.amsl.com>; Thu, 17 Feb 2022 09:34:32 -0800 (PST)
Received: from mailgate.go6lab.si (mailgate.go6lab.si [IPv6:2001:67c:27e4::18]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9DA13A0DB5 for <113attendees@ietf.org>; Thu, 17 Feb 2022 09:34:26 -0800 (PST)
Received: from mailgate.go6lab.si (localhost [127.0.0.1]) by mailgate.go6lab.si (Proxmox) with ESMTP id BA799816CE for <113attendees@ietf.org>; Thu, 17 Feb 2022 17:34:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=go6.si; h=cc :content-transfer-encoding:content-type:content-type:date:from :from:in-reply-to:message-id:mime-version:references:reply-to :subject:subject:to:to; s=mailgate; bh=gGukc1sx6yAzuFLj5j4a507U8 7YlZkpC/4r4E9kKMPY=; b=S0I5R/ANORjizcRyXQcq2TVcK3z74gVr0Acmsm0XO 4dx9ACJL19OKRb98kYtvya8NJqkdvzez4e6SrH/dlq4+ZJyOM++X5raTRhKJ+NG1 KOJYHJNJdJThehZ6HxkeXta1JpOxZOY/mIOYUlPEkyhK6FEH/18xZlFNU8zFfImT rmUavmsmAiGX1WBPNXHZzZ/2DTpc8GD/SFwGf4nkaZ/Tezn68LvdFI/iK/EtTeRn JnZsuxYizcWRELqStaDGGbCoWVibfL6SNbHJ28mNh17gPnF7uL9o9ZGlapQxmJVx O1vvH/vVpcz/srxtRvDjHZl8+K+52SPHV52xY2ox++JmQ==
Received: from mail.go6.si (mail.go6.si [IPv6:2001:67c:27e4::61]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate.go6lab.si (Proxmox) with ESMTPS id 9A0D5815FF for <113attendees@ietf.org>; Thu, 17 Feb 2022 17:34:22 +0000 (UTC)
Received: from [IPV6:2a00:ee2:e08:1b03:91cb:b87c:9c77:306c] (unknown [IPv6:2a00:ee2:e08:1b03:91cb:b87c:9c77:306c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jan) by mail.go6.si (Postfix) with ESMTPSA id 68784200FE for <113attendees@ietf.org>; Thu, 17 Feb 2022 18:34:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=go6.si; s=mail; t=1645119261; bh=URGgBla/4E2E8UNZOy2o5eIMj8LTfv6x1Dq7oORLKoQ=; h=Date:Subject:To:References:From:In-Reply-To:From; b=a2NnuXZnFp5/0C34TkV8dLkRCil9pBCUkqwtVw5Bg+kX0XUwwNGdA/R44Ia0toTR2 9ARVdjAsb3tCyN8TTsZdd3/VKJ+Yrb5B/hCF10+g7CLuR7XSukYPO54mmfo6WL9F2i xb8H/WieHCPzy/qQGo0RoC4IlaNVNSpS0D3cHBpM=
Message-ID: <07d87027-8162-b421-f157-6fff580d0b8b@go6.si>
Date: Thu, 17 Feb 2022 18:34:20 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1
Content-Language: en-US
To: 113attendees@ietf.org
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com>
From: Jan Zorz - Go6 <jan@go6.si>
In-Reply-To: <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/o491Wo1RaqGns0OxVRn9cixPUu0>
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: Thu, 17 Feb 2022 17:34:38 -0000

On 16/02/2022 11:35, Vittorio Bertola wrote:
> 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?

I'm also interested if someone from IETF meeting organization team could answer
this question...

Cheers, Jan Zorz

v2.23.0 | Report a Bug | By Email