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

Alvaro Retana <aretana.ietf@gmail.com> Thu, 05 March 2020 11:14 UTC

Return-Path: <aretana.ietf@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 C3EF83A12D3; Thu, 5 Mar 2020 03:14:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level:
X-Spam-Status: No, score=-1.096 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 aGYqeVxxWNSo; Thu, 5 Mar 2020 03:14:08 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 1F8503A12CF; Thu, 5 Mar 2020 03:14:08 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id a13so6266796edu.7; Thu, 05 Mar 2020 03:14:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=H+8L5u0CilapbiwiZSozuYLWKWGKEJgwhLm2a59eLmw=; b=DKbFKWmV4evKAJw/ehPyghHtD5XmQ5UXxLlxT1NQSpX3KSEnRLoBhXbeY8ojaAKfBQ YoigdhaSZHE5bhIzQKm1+91IZ38N4kkHwZf8bR/lbxuN6qczHgZ4uo3V83N5uMCReY5Z gdpMJrPH0ztzym5RAKyeFopEJjK6UGLoOKp2cOgXu/t/keB9waewXfXF25Vi5wFnJzk5 46bld1m/UsLnbRW8PqaLu0UG3DK3Ei6iU0BMlAejfE31XxO187jVkRoCYZ3aOAYbWC9x 1qj2OXeVN9nsO01y7aYc4n+HiGghAVg2/b7ZDASqfMxEOUYOKdJ+AbLzbeZXE11vaay8 BqaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=H+8L5u0CilapbiwiZSozuYLWKWGKEJgwhLm2a59eLmw=; b=oUQ54RcjpyoT3HzGUj1YniGKEpDM9CqKmt2EiZqW1qlPxQv/VEfZG7iNhpQFc5r7kY GeQgC5mmDflhMHQByFciPIkCyAJ7d/mCgeCuGr2Mlzj8A90zhmGV1khCzVeb0aiCLEs7 vu1zFFx6sQ13A5ULUzYEHoEx1KgNpemIsXV6uwkwu9de6ZNIyjZ9b3m2LVLr503t5Vq2 rug6nCnpxWmTdmwqeXRHEkQNSdHbcg97rEHwvrlCtZ0Qop+YjL6dOmVHO74LdhY0mTyX 7N/4q5scixGRRfIPiEkrWqeSUK8mlZuzqli9Gz/+cb/DGsriA3dgNy8kDkykpcbC8a5J BZkQ==
X-Gm-Message-State: ANhLgQ2OnOMf5Zl0oUmhAtOMCMI/fUS2SIP7FAmXUX1cA3P7kfV/meqn OlfaZllKTatI5wOVZx1D5O2ccrG6iQpU3ZDvJfk=
X-Google-Smtp-Source: ADFU+vv+LHt09fhOT7HWvCvyggNDK4Oc3kOWSOs1ruxEpyOkwBrfv0p0ikbhq9dEJ+nCDCKTxcoArvQVcqfSHwF0Sl0=
X-Received: by 2002:a17:906:9458:: with SMTP id z24mr7100575ejx.155.1583406846546; Thu, 05 Mar 2020 03:14:06 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 5 Mar 2020 11:14:05 +0000
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <B0D26E9A-0B21-49C3-9D48-EC2C638CB83D@gmail.com>
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>
MIME-Version: 1.0
Date: Thu, 05 Mar 2020 11:14:05 +0000
Message-ID: <CAMMESsxqOdzWNm=aTz9yfmfz-154OO5KWVuoTfsMdG-oRpLDTA@mail.gmail.com>
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
To: Robert Raszuk <robert@raszuk.net>, "exec-director@ietf.org" <exec-director@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009f991405a019a214"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HiMlIxkfsg8SeSeHy7k1eDdy2EQ>
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 11:14:10 -0000

Stewart/Robert:

Hi!

Please don’t loose sight of this other piece of text in Jay’s message: "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.”

Yes, we are very aware of the restrictions, which can affect anyone and are
looking into it.

The situation is obviously very fluid.  Please bear with us.

Thanks!

Alvaro.

On March 5, 2020 at 5:17:41 AM, Stewart Bryant (stewart.bryant@gmail.com)
wrote:

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 on behalf of 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
>     [2]
> https://www.who.int/ith/2019-nCoV_advice_for_international_traffic-rev/en/
>     [2] https://www.ietf.org/how/meetings/107/ietf107-health-measures/
>     [3] https://www.youtube.com/watch?v=SAo9Nooi69E (about 55 minutes in)
>     [4]
> 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
>     [6] https://www.ietf.org/registration/ietf107/attendance.py
>
>     --
>     Jay Daley
>     IETF Executive Director
>     exec-director@ietf.org
>
>     --
>     107all mailing list
>     107all@ietf.org
>     https://www.ietf.org/mailman/listinfo/107all
>
>
>