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

"Carlos M. Martinez" <carlosm3011@gmail.com> Thu, 05 March 2020 02:44 UTC

Return-Path: <carlosm3011@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 E49913A0935; Wed, 4 Mar 2020 18:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 E-DxaacCDBKe; Wed, 4 Mar 2020 18:44:12 -0800 (PST)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 738CC3A0932; Wed, 4 Mar 2020 18:44:12 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id e20so3079878qto.5; Wed, 04 Mar 2020 18:44:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Mw+sQ8vBCSbfR+E6Lp816bfkVl6Hs9dDYXv1+pK+QdA=; b=IpepO+8Z55Z4OPsckXCf6JR+E1PepwQBhdhBllTjEeaetcg6E7Fntq0TLuuVcX4Vlx l2kFgPNmtJv27L3Y4Htge3SC/NSYsBdcCbWC3dNusE9/XElW8s+LgiwP1Wn3MnkhbChL cZh+YNB1ruOiEwSTgo5sBw7mFV4+vHoqvq6OBvLJm0pmWobNPdCTj/MzRKJhcfEAp1Cz aCKhAgMmppvMTFoArJDoAC2HB43ZaqX6Ora0derHZcRizzIRRJT2hlg6NCmD8d+HRP8a NdquRG6+FuTzYhgJZQVwpkHKFT38O0hQNnMGk0jNC1tVOeYRPJfVJNqqejQS3Olnn0Z2 ql1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Mw+sQ8vBCSbfR+E6Lp816bfkVl6Hs9dDYXv1+pK+QdA=; b=NbHc1lGoB6wWaG802ee0vjmnBugXKkutJUpOm9kXEfVqBQsFSbL+Yh1hVT0O583VY9 ufj64U+igwJz8h0QuzFVXY15mCruwDA351BoWXbm8Qq/jh3a7FQwKRntzZLqOcI+y9D8 18/0DeVldhmRwjhk1gqaSriGjbt/nriBUg5N4hwYk/Q3dTQbYwa0InDK2Vm6cBfBeR8B 2IkvubBG56+GiWZsZrLsGy5UTXdDoQvwMH2iOqB0Aw7q9no/5qgLsShgxPJaU6aDIm3p sSTIULo0OkbCu3/P0glsVGjyvBdVH1r8+WFLN5AWTjFeaUgY0e9g6jvHln4G6LD9+Gql ZcNA==
X-Gm-Message-State: ANhLgQ1dugHkHf0rM2u+mz3gr911glU1bD/hwhIDhr08vMpUyx98Q4Pt 2g2317DGT/KmZCVhLoUc20Ma+e9IiVmAkA==
X-Google-Smtp-Source: ADFU+vsegpHJxLGbfEqNx26Is5+fRpWTFACGEEYaDZvsW2UffYDXDFL9L5t2Bp+CabZdWR3HWYVQOg==
X-Received: by 2002:ac8:6e88:: with SMTP id c8mr5411563qtv.40.1583376251221; Wed, 04 Mar 2020 18:44:11 -0800 (PST)
Received: from [200.10.63.158] ([2800:a4:287e:a600:41ec:18e8:a5e:f065]) by smtp.gmail.com with ESMTPSA id x19sm14882371qtm.47.2020.03.04.18.44.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Mar 2020 18:44:10 -0800 (PST)
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
Cc: Warren Kumari <warren@kumari.net>, Robert Raszuk <robert@raszuk.net>, IETF <ietf@ietf.org>, exec-director@ietf.org
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
Date: Wed, 04 Mar 2020 23:44:07 -0300
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <E0E646D3-6F77-4935-BB79-55ECED3766A3@gmail.com>
In-Reply-To: <e863cb46-f4ae-b99d-481b-d5bc51ee5062@petit-huguenin.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> <CAHw9_i+yuojs6gkX+GmP8xCxPZn_MBvZH66YHf42bM6Xsip4-Q@mail.gmail.com> <e863cb46-f4ae-b99d-481b-d5bc51ee5062@petit-huguenin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l4bVzFpni0EcoDVV_C-zAzuyeJ0>
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 02:44:15 -0000

Same here, would be happy to help. Still planning to be in Vancouver.

On 4 Mar 2020, at 21:50, Marc Petit-Huguenin wrote:

> Happy to help if needed.
>
> "Et s’il n’en reste qu’un, je serai celui-là !"
>
> On 3/4/20 4:33 PM, Warren Kumari wrote:
>> On Wed, Mar 4, 2020 at 6:50 PM 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.
>>>
>>
>> Simply because the chairs cannot make it does not automatically mean 
>> that
>> the WG meeting is cancelled -- WGs chairs can ask the WG secretary, 
>> or
>> appoint a temporary secretary or just ask an in-person participant to 
>> do
>> the physical onsite things, like bluesheets, pushing the big red 
>> button,
>> etc.
>>
>> W
>>
>>
>>
>>>
>>> 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
>>>>
>>>>
>>>>
>>