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

Stewart Bryant <stewart.bryant@gmail.com> Thu, 05 March 2020 10:17 UTC

Return-Path: <stewart.bryant@gmail.com>
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 04CD33A0A86; Thu, 5 Mar 2020 02:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, 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=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 BKrSh8O5PvwA; Thu, 5 Mar 2020 02:17:08 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 82A3B3A0A82; Thu, 5 Mar 2020 02:17:08 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id v11so4307283wrm.9; Thu, 05 Mar 2020 02:17:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kRvjzXcyDxDeXjW4i77H1G/sQQHTRVhvMAO1AmwzUQ0=; b=jb3mZax8vmLI9zQpkqhaA/maaEClQeLdd5MAf2SYOxPTkoBEiZadvUM4yEPKrODu85 JaWXXSSnZi/zxaroDwBSRFnAofz9hwWEFbpBagbcB3A4o/nm53ljcLbp9uAQcnISe9Bu 8sIyGnlBYrwWQ2W185QNtedd/rs1c+Zd8CV7jgidLqlB1spYo7S/9GHZlT+PtVLbHr5P ExTUT/mGUCQWt+LD2yLnLXCnegVdF5ZzBhHkFxxD1UWSBBcW40m/kioS4HUZH+8fEPoq wH2lnKgc7LK1YcEBiumgZn5HHsgLFLPhTHG/Bfd7ZSyN6RNqNd6Ijja1sGmLIweAWACp ZJKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kRvjzXcyDxDeXjW4i77H1G/sQQHTRVhvMAO1AmwzUQ0=; b=p9FsZmj+Kcp4F2yDvg7WyX/GSERUmRj6e+ZEyLj41OYYMaPyAAdmxlCG96R6jcKKs+ vmqZhKSHKg8LGRvinSUxFkOOkD19ivIYUJ9GKfQ0tXEILC5lteGxDIEERHeyS5DbDFqs ocPtP4c7kv8KaREapSnabUR7HJoEnxaYLMUbjDIHFofUFx8Aj9uy3RUiYQGB1GCwlPMH jLGzPm+vEwtzRw8JAybcKEt3x9/D8BbDcVfLS5BCz8rOWzb/ZsTt6XBlFbTgP3L63bmN G1l6kuv5x6rIsBKgKyzu5oWUjUhxClqDXG/J+WUMiFei3jcETxhg27Gf1ONThpHyg/n+ CdxA==
X-Gm-Message-State: ANhLgQ0aOC2hPYRylby4FviNmczxq7F5YPJkkyQ9BKVwZbpe4a9g2S/X F7EV61eXAJdBIEvCcHAd7Oem+nqH
X-Google-Smtp-Source: ADFU+vvlw85BHyw7kRnIE41dlTY0G/9tEQORpeh3gn0l/jhx2Ww/7VnahcX4/JaKw3t21xPR6+3sqA==
X-Received: by 2002:a5d:4491:: with SMTP id j17mr9849269wrq.152.1583403426902; Thu, 05 Mar 2020 02:17:06 -0800 (PST)
Received: from [192.168.178.46] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id b16sm40471416wrq.14.2020.03.05.02.17.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Mar 2020 02:17:06 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <B0D26E9A-0B21-49C3-9D48-EC2C638CB83D@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E9471D1-5BDE-400C-B91C-737260E97F4D"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
Date: Thu, 05 Mar 2020 10:16:35 +0000
In-Reply-To: <CAOj+MMG+OhM9_G3+ikfGxXSqi6PMO0EJeZ=vCC3Wne=YWHLLhg@mail.gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF <ietf@ietf.org>
To: Robert Raszuk <robert@raszuk.net>, "exec-director@ietf.org" <exec-director@ietf.org>
References: <158335136585.29295.1109218817393181187@ietfa.amsl.com> <D4FDE701-CE29-44BE-877A-B45266FEFF08@cisco.com> <CAOj+MMG+OhM9_G3+ikfGxXSqi6PMO0EJeZ=vCC3Wne=YWHLLhg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q4tnsjoPia3LRdOQVXnDB_NaPW8>
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 10:17:11 -0000

I must say I am becoming increasingly worried about the viability of this meeting.

With the big company bans, it is not clear how many of the senior leadership will be at the meeting. Is there a roll call of IESG members that will be present?

There are 619 people registered for on-site. If we discount those from companies that have already declared that they are not permitting their staff to travel, what is the number?

Best regards

Stewart


> On 4 Mar 2020, at 23:50, Robert Raszuk <robert@raszuk.net> wrote:
> 
> All,
> 
> > We are aware that more companies have imposed travel restrictions and in some cases 
> > those are dependent on who else will be attending the conference.  
> 
> As it has already started to happen today for BESS WG it only takes two chairs to work for company which imposed travel policy not to be able to travel to run the WG meeting. if they can not travel the WG meeting is cancelled. 
> 
> I quite do not understand how IETF director(s) keep the event ON in such situation. 
> 
> And what is worse - some meetings may be cancelled last minute or chairs may be not able to travel last minute as well. 
> 
> In what light does this put potential attendees ? 
> 
> Many thx,
> Robert.
> 
> 
>  
> On 3/4/20, 11:50 AM, "107all on behalf of IETF Executive Director" <107all-bounces@ietf.org <mailto:107all-bounces@ietf.org> on behalf of exec-director@ietf.org <mailto:exec-director@ietf.org>> wrote:
> 
>     This is a further update on IETF 107 Vancouver and the ongoing situation with COVID-19 (Coronavirus).
> 
>     It is still our intention to go ahead with IETF 107 Vancouver as the public health advice remains that we do not need to cancel conferences in Vancouver or avoid travel to Vancouver.  The Public Health Agency of Canada (PHAC) continues to classify the risk of infection in Canada as low [1] and the World Health Organization (WHO) continues to recommend against travel restrictions [2].  As shared earlier, special measures are being put into place for IETF 107 in Vancouver following public health recommendations for meetings of this nature [3]. 
> 
>     We continue to monitor the situation and will respond quickly if the public health advice changes.  While it is clear that the situation is deteriorating, the public health advice from the WHO, which is very consistent and evidence-based, is that local containment of outbreaks is both feasible and demonstrated to work.  To hear more about the evidence-based guidance being provided by the WHO we recommend watching a WHO press briefing [4] or reading their daily situation reports [5].
> 
>     We are aware that more companies have imposed travel restrictions and in some cases those are dependent on who else will be attending the conference.  However, we will not be imposing travel restrictions on IETF participants from specific countries or regions as it is for the Canadian government to decide who can enter their country.
> 
>     The current PHAC advisory page for visitors [6] is that those arriving from Hubei province of China or from Iran should self-isolate for 14 days on arrival and monitor their health.  That advisory may be updated at any time and so we advise anyone travelling from a country with an infection cluster to check that page before travel.
> 
>     We continue to receive new registrations every day but those are now being offset by cancellations and the number of registered in-person participants is hovering at around 625 [7] with over 200 registered remote participants.  The Internet Engineering Steering Group (IESG) and IETF Administration LLC continue to monitor the situation and the IESG is currently seeking input from working group and research group chairs to understand the extent of expected session cancellations. 
> 
>     If we are required to cancel then the IESG is considering options for virtual meeting support, which it will report on in due course.
> 
>     Please feel free to contact me directly if you have any questions or comments.
> 
>     [1] https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection.html <https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection.html>
>     [2] https://www.who.int/ith/2019-nCoV_advice_for_international_traffic-rev/en/ <https://www.who.int/ith/2019-nCoV_advice_for_international_traffic-rev/en/>
>     [2] https://www.ietf.org/how/meetings/107/ietf107-health-measures/ <https://www.ietf.org/how/meetings/107/ietf107-health-measures/>
>     [3] https://www.youtube.com/watch?v=SAo9Nooi69E <https://www.youtube.com/watch?v=SAo9Nooi69E> (about 55 minutes in)
>     [4] https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports/ <https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports/>
>     [5] https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection/latest-travel-health-advice.html <https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection/latest-travel-health-advice.html>
>     [6] https://www.ietf.org/registration/ietf107/attendance.py <https://www.ietf.org/registration/ietf107/attendance.py>
> 
>     -- 
>     Jay Daley
>     IETF Executive Director
>     exec-director@ietf.org <mailto:exec-director@ietf.org>
> 
>     -- 
>     107all mailing list
>     107all@ietf.org <mailto:107all@ietf.org>
>     https://www.ietf.org/mailman/listinfo/107all <https://www.ietf.org/mailman/listinfo/107all>
> 
>