Re: Further update on COVID-19 (Coronavirus) and IETF 107 Vancouver
Donald Eastlake <d3e3e3@gmail.com> Thu, 27 February 2020 19:29 UTC
Return-Path: <d3e3e3@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 1F60A3A09FD for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 11:29:50 -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 Vhkh2Wne3iS3 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 11:29:48 -0800 (PST)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 5CF803A09AF for <ietf@ietf.org>; Thu, 27 Feb 2020 11:29:48 -0800 (PST)
Received: by mail-io1-xd2a.google.com with SMTP id z190so767085iof.1 for <ietf@ietf.org>; Thu, 27 Feb 2020 11:29:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=0rILHT7cWqDxirSAs6ISL0g8TeicuiJZRg9+s0gmq/k=; b=m242Eh1SkrHvIRsS37RxMEes+o+BVkgUDr1l0IdafpcXEdPZBKedhVvRIn7QmRWYoF vzqrAL4f97nc3UlH9ClxkxZBArFRywpeC810G0cIf0D9nGorjb6KCEkGZsqilNAZB0M/ +d7HifPJOsJjNlR6TMJrEx7vzwUj0cP6ggDsWAzQcGyv6NRWHG6DZRydQ1OoGh1QnRx7 FTaXWazrHJ/xMrQ9FFuZAts35MZaz3eOavIfSRww6nalY50QoOeFErQh56triLwya+Jk SI8cgmsAvPAQpfxcfy/LM8Hwf7aeZZhaNomPR1q+Z3fR50puhu5ORRjQUYHwT9oZKYs2 ASLA==
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:content-transfer-encoding; bh=0rILHT7cWqDxirSAs6ISL0g8TeicuiJZRg9+s0gmq/k=; b=ny7Za/Urnv5i/aRFcOxnKnsq6zg8eAnneu01S6aDFHHsntwpWsHzr3w6ih1vEGBxUW YG00K3qWZjhZ1sy8tlcppem/jrj8/RKEgCnWpqbYiYk74I01DhGbVUth5lGh6GxTcFMx eDaFGhSQ7L87B0b2GjUfS8maP4R2HOSxqMbzUm+mOc/OpsQPku6yecQloQTE/ISId1sO OubJrpKzNMDmD0Zylzmzgrnvd6oTdp7tZ0YwfeVAq9kTOZdbwYUR4QXhy3zXVMnTbyHP N1DXglKdq73XQ5tNTfOmMzAPXxuKHuvFFnln9UNYSYOx4z+OIosYnyTDQ6k+mULHQ6jO RBxA==
X-Gm-Message-State: APjAAAWEEDBf14rj3s9lInApAFJV7YhE0NEEJFkCmGxV2Thg0OVOSuQT lBUfBf+r89RauYNIkGEcqnVpR4VO1C5rZZpIgZ8=
X-Google-Smtp-Source: APXvYqz+11uclIMxLd6wvjc/iqHE5NGJCPHQHPtzdCxRBDljZiHNtFIS4KIenWnU4G2sqtBDr0FFJkH6YkmnQzLIZGk=
X-Received: by 2002:a02:c6d4:: with SMTP id r20mr347151jan.96.1582831787573; Thu, 27 Feb 2020 11:29:47 -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: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 Feb 2020 14:29:35 -0500
Message-ID: <CAF4+nEF0gr7RTgNd0RT67POyrX1QaZr4BtTFhQsjMpWpsfhnjQ@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: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gxf9F6EAaNGg6rrCt_qODorsVpQ>
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 19:29:50 -0000
I believe that a reasonable number of face-to-face meetings per year is essential to much of the progress made in the IETF. Remote participation tools do not work nearly as well as face-to-face meetings even for WG meetings and the like and are pretty hopeless for hallway meetings and most of the spontaneous or planned on the spot side meetings. The deadlines for a face-to-face meeting act as a useful forcing function to get drafts posted and the like. The optimum number of meetings per year is an interesting question. Over a considerable range, I believe the more meetings the more progress and the greater the likelihood of achieving schedules but also the higher the expense which acts as a restriction on participation. The fewer meetings, the cheaper/easier participation is but the more things tend to draft. Here are how many ~1 week meetings per year some standards organizations have that I happen to know about: 3GPP 8 meetings IEEE 802 WGs 6 meetings Broadband Forum 4 meetings IETF 3 meetings So, I think the IETF's 3 meetings a year is pretty close to optimal for the IETF. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com On Thu, Feb 27, 2020 at 5: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