Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Alexander Pelov <a@ackl.io> Thu, 27 February 2020 10:52 UTC
Return-Path: <alexander@ackl.io>
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 C68503A086C for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 02:52:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ackl-io.20150623.gappssmtp.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 JO4fgeUXNsPI for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 02:52:17 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 F39553A0866 for <ietf@ietf.org>; Thu, 27 Feb 2020 02:52:16 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id n21so2644798ioo.10 for <ietf@ietf.org>; Thu, 27 Feb 2020 02:52:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q+rRT+/6BqqG13vFkl0swKHjGC1fnXT+ZjZaCSQHb5M=; b=mKRGF4dtjQZhiZ7XaKezXdjtbWZYEM73kEF0o+EUbFdu3pCpUgjkFqliHfDg2tu6yw vCFxIJ6qfkHL5Y7oxnS8xP0KcbxEClaLNKAx/A+xnpZr8lBDrL5z/q+ETLVGPl4QHVwb eEOkqzbQzSrsq/+QePiAV3FsIMdmRpN8V9muVp8IK93M7mhJjbbPQJN8wMil3JjYczdL 3OsIFZM42t95cXjuM/7cJz+3ETktMsQdKSUh0vPN+QuiVTJd38MQJUexIATdTA2OPYm2 kToPtK9Sc5TDMiw/RXAv1u37dWD3BTLl2rJLJI9zNv5rr9bNMK0yvDetW3NWblboNlNP zHfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q+rRT+/6BqqG13vFkl0swKHjGC1fnXT+ZjZaCSQHb5M=; b=L1cG48u+e2Lc3bIntV02J9KIdBVlBiS+PJLeTLict5XgrAf4cmHtS9tnLsKajQ/gWJ hAhJMF4N7D/jSETN6T7SVE25IC2h+AeeewZM0NxoeDmXOpbvdbnKoyI3pDKhGjlgM6Le eZjAtaY181LdKi8g/sLFz9cXTC9dXtFx9XER0RVqJeKdRwAzh0B58tFjVYFLSi2NciVs d+1yit/VwsHzzD63J+lfX6ESP2H8vJFYW6n0tTKqSJfa/IbsouS1mf6gD9TXnHHhZR41 3l8ER7BnpAIvbalZBr47Ve5y1YezT4e1wmFSu1TpT/SWEG9GAfHF20Q5NL2w+8kPcUtb MWrA==
X-Gm-Message-State: APjAAAUNaLOwO+87lf8fqFh2+fpjaXFWHDlEiLHOk2bQGZZGo14JEQNS khEwxFz40bIwyO4smk6uvfk7uA5bHH8ZjUgmqH3HwZpTmkTdjw==
X-Google-Smtp-Source: APXvYqwux7gilVT6FQ+Wz1Uqk8KpWsJzoajSkQLkAg+KY9lJeqcmmr/QwVknb6E/iH7Ly8WWkdX6kXTvT5VK2cld1uU=
X-Received: by 2002:a5e:a616:: with SMTP id q22mr3688031ioi.250.1582800734927; Thu, 27 Feb 2020 02:52:14 -0800 (PST)
MIME-Version: 1.0
References: <158258721017.24319.9082233711977122647.idtracker@ietfa.amsl.com> <CAAObRXJ=NnrxLAGgtas8Cs_jw-AJ0YsgYpMmYtrHy+PjKsfqvg@mail.gmail.com> <CAMm+Lwh17iOi_8qZ7at8gHQ6R38YwVuUZ8O1cpsJU7MKh+nMmA@mail.gmail.com> <DBBPR03MB5415B842B32E90BF91D0C361EEEA0@DBBPR03MB5415.eurprd03.prod.outlook.com> <CAAuWHCKRhe-ct2tP5TqBaCn_fSTBoFSkrppTKOyhoP_xW6Ydag@mail.gmail.com> <DM6PR05MB634809ED4CD6D49036B47A25AEEA0@DM6PR05MB6348.namprd05.prod.outlook.com> <6E58094ECC8D8344914996DAD28F1CCD27DA0AFB@dggemm526-mbx.china.huawei.com> <500287902.17362.1582797595605@appsuite-gw1.open-xchange.com>
In-Reply-To: <500287902.17362.1582797595605@appsuite-gw1.open-xchange.com>
From: Alexander Pelov <a@ackl.io>
Date: Thu, 27 Feb 2020 11:51:24 +0100
Message-ID: <CACQW0EoRqAbDYSCnr4Q+FPHfcqfGMtx0f73dzB5XEdK21AGZcQ@mail.gmail.com>
Subject: Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Cc: "Roni Even (A)" <roni.even@huawei.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008e5a4b059f8c832a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y_SnbSVzCFTGtI77JxhW3565fKI>
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, 27 Feb 2020 10:52:24 -0000
Dear all, I find that all the topics and the mails quite interesting, well-thought and informative. In addition, I find the proposed IETF Policy to be reasonable and a good start. There are three topics that seem to get mixed: 1) Do we cancel the on-site IETF 107 Meeting? 2) Do we transform it into an all-virtual meeting? 2.1) Pros-and-cons of virtual meetings 2.2) Logistics of organizing a fully virtual IETF meeting 2.3) Do we accept a "degraded virtual IETF 107" ? 3) Generalizing the current situation (e.g. have all future IETF meetings remote, etc. etc.) 2.1) and 3) can be addressed later - let's not boil the ocean. We need to consider 1) seriously - and it is an event we cannot control, nor quantify correctly. (I've witnessed this first-hand having been forced to cancel two business trips a week before the event (one of which was MWC)). I think that we should consider either: A) preparing a full operational plan for all-virtual meeting or B) being ready to cancel IETF 107. A) doesn't need to be a perfect plan. However, if we do not have A), we should be ready to accept that B) can happen. The question can then be simplified to: *How much time would it take to put in place a workable plan to have all-virtual IETF 107?* If it would take 7 days, then we have until March 13th to react to 1). If it would take 1 month, it's already too late. In both cases, there is a cut-off date for cancellation decision, and I'd love to know when that date would be. One thing about the logistics of a fully virtual IETF meeting is to have the right communication tools, and I'd add WG chair & AD preparation. (I'd expect things to work smoothly, but I don't like discovering surprises on the day of the meeting). Also, Hackathon preparation (or cancellation ?) My 0.02€ Cheers, Alexander On Thu, Feb 27, 2020 at 11:01 AM Vittorio Bertola <vittorio.bertola= 40open-xchange.com@dmarc.ietf.org> wrote: > > Il 27/02/2020 08:33 Roni Even (A) <roni.even@huawei.com> ha scritto: > > > Hi, > > I participated in tsvwg virtual meeting last week that had about 30 > participants using IETF webex.. If this is a demonstration of holding a > virtual meeting in my view we are not ready. I kept losing the audio of the > meeting and I was not alone, others complained in the chat window. The > suggestion was to use a PSTN connection to the meeting and not the IP one. > This mean that I will have to pay for international call since there was no > local free call in number. Note that it was an audio only plus data, no > video. > > As ICANN (who has decided to go fully online) is discovering, even if you > solved the infrastructural problem (which they apparently plan to solve by > using Zoom), there are many problems in running a purely virtual meeting, > in addition to the basic ones of missing all the informal interaction, > which is usually key to getting the hardest issues solved, and of crippling > the emotional and non-verbal communication, which leads much more easily to > confrontation. > > For example, the timezone problem: no matter which timezone you are in, > there will be people for which the meeting will be out of working hours, > often during the night. While your employer and your family will accept to > "lose" you for a week if you go physically elsewhere, it is much harder to > get that accepted if you are home - they will easily still expect you to be > available during the day at least for important stuff. As a minimum, your > attention will be partly diverted and your physical state will be hampered, > and as a maximum, you will miss good chunks of the meeting. In some cases, > working at night would even be incompatible with local labour laws. > > Or the connectivity problem: possibly this is stronger for ICANN, which > has a significant share of participants from parts of the world where > connectivity is worse, but not everyone has broadband connectivity readily > available; actually, many African participants told ICANN that they do not > have any connectivity at home, and they only connect from an office which > will be closed during the daytime of the timezone of the meeting. And if > they have connectivity, e.g. through mobile networks, it's often > prohibitively expensive for day-long connections. Actually, if you end up > having to use good old telephone calls, it will often be prohibitively > expensive even in the "developed" world; and while travel is even more > expensive, funding for travel is often available in ways that funding for > (personal) connectivity is not. > > More generally, people with worse connectivity will have harder times in > understanding others (especially if English is not their mother tongue), > being given the floor, making their points, gaining support for them etc > (though some careful chairmanship could partly address this). > > I'm not saying that these problems cannot be addressed, but it's important > to consider them; it's false that meeting online always increases > opportunities for participation, it just creates a different set of > problems and of disadvantaged people. > > P.S. Now for the less topical part - sorry but I have to say this: > > > Il 26/02/2020 02:00 Casey Farrell <caseyfarrell26@gmail.com> ha > scritto: > > > > > https://www.yahoo.com/news/san-franciscos-mayor-declared-state-225239441.html > > It's nice to see that politicians overreacting and spreading panic > globally just to show their local voters that they "do something about it" > are not a prerogative of Italy only! > > -- > > Vittorio Bertola | Head of Policy & Innovation, Open-Xchange > vittorio.bertola@open-xchange.com > Office @ Via Treviso 12, 10144 Torino, Italy > >
- Re: Further update on COVID-19 (Coronavirus) and … Arleen Elliott
- Re: Further update on COVID-19 (Coronavirus) and … JORDI PALET MARTINEZ
- Re: Further update on COVID-19 (Coronavirus) and … Stephane Bortzmeyer
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- RE: Further update on COVID-19 (Coronavirus) and … Belotti, Sergio (Nokia - IT/Vimercate)
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- RE: Further update on COVID-19 (Coronavirus) and … Belotti, Sergio (Nokia - IT/Vimercate)
- Re: Further update on COVID-19 (Coronavirus) and … Stewart Bryant
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Mary B
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Mary B
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Stephane Bortzmeyer
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Kathleen Moriarty
- Re: Further update on COVID-19 (Coronavirus) and … John C Klensin
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Tim Bray
- Re: Further update on COVID-19 (Coronavirus) and … Alexandre Petrescu
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Kathleen Moriarty
- Re: Further update on COVID-19 (Coronavirus) and … Nico Williams
- Re: Further update on COVID-19 (Coronavirus) and … Michael StJohns
- Re: Further update on COVID-19 (Coronavirus) and … Nico Williams
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Davey Song
- Re: Further update on COVID-19 (Coronavirus) and … Phillip Hallam-Baker
- RE: Further update on COVID-19 (Coronavirus) and … Andrew Alston
- RE: Further update on COVID-19 (Coronavirus) and … Belotti, Sergio (Nokia - IT/Vimercate)
- Re: Further update on COVID-19 (Coronavirus) and … tom petch
- Re: Further update on COVID-19 (Coronavirus) and … Marc Petit-Huguenin
- Re: Further update on COVID-19 (Coronavirus) and … Joseph Potvin
- What can IETF do? Re: Further update on COVID-19 Phillip Hallam-Baker
- Re: What can IETF do? Re: Further update on COVID… Joel M. Halpern
- RE: What can IETF do? Re: Further update on COVID… Larry Masinter
- Re: What can IETF do? Re: Further update on COVID… Spencer Dawkins at IETF
- Re: What can IETF do? Re: Further update on COVID… Phillip Hallam-Baker
- RE: Further update on COVID-19 (Coronavirus) and … Ron Bonica
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: Further update on COVID-19 (Coronavirus) and … Jared Mauch
- Re: Further update on COVID-19 (Coronavirus) and … Warren Kumari
- Re: Further update on COVID-19 (Coronavirus) and … Robert Raszuk
- Re: Further update on COVID-19 (Coronavirus) and … Kathleen Moriarty
- Re: Further update on COVID-19 (Coronavirus) and … Carlos M. Martinez
- Re: What can IETF do? Re: Further update on COVID… Nick Hilliard
- Re: What can IETF do? Re: Further update on COVID… Joseph Potvin
- Re: What can IETF do? Re: Further update on COVID… Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Victor Kuarsingh
- Re: What can IETF do? Re: Further update on COVID… Jay Daley
- Re: What can IETF do? Re: Further update on COVID… Keith Moore
- Re: What can IETF do? Re: Further update on COVID… Richard Barnes
- Re: What can IETF do? Re: Further update on COVID… Phillip Hallam-Baker
- Re: What can IETF do? Re: Further update on COVID… Andrew G. Malis
- Re: What can IETF do? Re: Further update on COVID… Melinda Shore
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: What can IETF do? Re: Further update on COVID… Joseph Potvin
- Re: Further update on COVID-19 (Coronavirus) and … Jay Daley
- Re: What can IETF do? Re: Further update on COVID… Spencer Dawkins at IETF
- Re: What can IETF do? Re: Further update on COVID… Phillip Hallam-Baker
- Re: What can IETF do? Re: Further update on COVID… Joseph Potvin
- RE: Further update on COVID-19 (Coronavirus) and … Roni Even (A)
- RE: Further update on COVID-19 (Coronavirus) and … Vittorio Bertola
- Re: Further update on COVID-19 (Coronavirus) and … Alexander Pelov
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: Further update on COVID-19 (Coronavirus) and … Rich Kulawiec
- Re: Further update on COVID-19 (Coronavirus) and … Livingood, Jason
- Re: Further update on COVID-19 (Coronavirus) and … Stewart Bryant
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Nick Hilliard
- Re: Further update on COVID-19 (Coronavirus) and … Carlos M. Martinez
- Re: Further update on COVID-19 (Coronavirus) and … Fred Baker
- Re: Further update on COVID-19 (Coronavirus) and … Phillip Hallam-Baker
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Christian Hopps
- Re: Further update on COVID-19 (Coronavirus) and … Donald Eastlake
- Re: Further update on COVID-19 (Coronavirus) and … Carsten Bormann
- Re: Further update on COVID-19 (Coronavirus) and … Spencer Dawkins at IETF
- Re: Further update on COVID-19 (Coronavirus) and … Phillip Hallam-Baker
- Re: Further update on COVID-19 (Coronavirus) and … Christian Hopps
- Cookies as a transmission vector [was: Re: Furthe… John Scudder
- Re: Further update on COVID-19 (Coronavirus) and … Joseph Potvin
- Re: Further update on COVID-19 (Coronavirus) and … Bob Hinden
- Re: Further update on COVID-19 (Coronavirus) and … Michael Richardson
- Re: Further update on COVID-19 (Coronavirus) and … Joseph Potvin
- RE: Cookies as a transmission vector [was: Re: Fu… Ron Bonica
- Re: Cookies as a transmission vector [was: Re: Fu… Kathleen Moriarty