Re: [107all] Update on IETF 107 Vancouver and COVID-19

Jared Mauch <jared@puck.nether.net> Thu, 05 March 2020 12:02 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2503A1059; Thu, 5 Mar 2020 04:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 1YIhtMLexzkU; Thu, 5 Mar 2020 04:02:18 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D34A43A0CC9; Thu, 5 Mar 2020 04:02:18 -0800 (PST)
Received: from [10.0.0.129] (c-68-32-79-179.hsd1.mi.comcast.net [68.32.79.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 03575540216; Thu, 5 Mar 2020 07:02:17 -0500 (EST)
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Content-Type: text/plain; charset="utf-8"
From: Jared Mauch <jared@puck.nether.net>
X-Priority: 3
In-Reply-To: <417138205.25757.1583409298775@appsuite-gw2.open-xchange.com>
Date: Thu, 05 Mar 2020 07:02:16 -0500
Cc: Carsten Bormann <cabo@tzi.org>, Stewart Bryant <stewart.bryant@gmail.com>, IETF <ietf@ietf.org>, "exec-director@ietf.org" <exec-director@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7F6A0E7-0F1C-4D02-B7B6-8503BDA1B4E8@puck.nether.net>
References: <158335136585.29295.1109218817393181187@ietfa.amsl.com> <D4FDE701-CE29-44BE-877A-B45266FEFF08@cisco.com> <CAOj+MMG+OhM9_G3+ikfGxXSqi6PMO0EJeZ=vCC3Wne=YWHLLhg@mail.gmail.com> <B0D26E9A-0B21-49C3-9D48-EC2C638CB83D@gmail.com> <213A9519-5989-498B-BAFA-390BC4E57960@tzi.org> <417138205.25757.1583409298775@appsuite-gw2.open-xchange.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vu8ABmnxDPlgHLLV_WKtigxaNRM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2020 12:02:20 -0000


> On Mar 5, 2020, at 6:54 AM, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
> 
> 
>> Il 05/03/2020 12:18 Carsten Bormann <cabo@tzi.org> ha scritto:
>> 
>> It would be really useful if people who won’t come could transfer themselves from the local to the remote attendance part, in the attendance list or in a separate statistic.
> 
> To be honest, I think that many of us who already registered for physical attendance still do not know if they will come or not. Given how fluid things are, people are likely to wait almost until the deadline (likely, the hotel cancellation one, since most flights will be non-refundable anyway) before making a final decision; and company/public policies may change without notice.
> 
> Also, even if you think "at 90% I won't come", you still don't transfer/cancel your paid registration until that 90% becomes 100%. Perhaps it could be useful (if it can be implemented promptly) if in-person registered attendees had a special form in the registration area to enter and update their current estimated likelihood of actually making it to Vancouver; even if only a share of the attendees did it, it would provide a rough guess.


I want us to all be conscious that speculating about each others attendance or asking the IETF Exec Director and registration team do additional work in this regard likely doesn’t contribute much.

They already indicated that the cancellations are at the same rate as new registrations.  Many of us likely need to travel regardless, or do not have travel restrictions short of a public health declaration.  My company does not have any restrictions in place other than directly into certain cities.  Thankfully my travel to mainland china isn’t booked :-)

Please let the Exec Director and support teams do their jobs.  The Meetecho team are professionals in the audio and AV as well.

I am certain they are working very hard behind the scenes and I appreciate the transparency.

- Jared