Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 13 May 2020 18:40 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43E493A076F for <manycouches@ietfa.amsl.com>; Wed, 13 May 2020 11:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.395
X-Spam-Level:
X-Spam-Status: No, score=-1.395 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 lgTzDd4MiH_e for <manycouches@ietfa.amsl.com>; Wed, 13 May 2020 11:40:24 -0700 (PDT)
Received: from mail-ot1-f47.google.com (mail-ot1-f47.google.com [209.85.210.47]) (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 B26153A076C for <manycouches@ietf.org>; Wed, 13 May 2020 11:40:24 -0700 (PDT)
Received: by mail-ot1-f47.google.com with SMTP id z17so235463oto.4 for <manycouches@ietf.org>; Wed, 13 May 2020 11:40:24 -0700 (PDT)
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=2pOTG1kKtl7wDNIrYoo4P7oEoURU1heI5IP3at8jSxY=; b=YgKADdP9Nto9A1kOmTYsNhMb5DVIeL0sLB4tDAcvZ7DCprn9fjcBA6WPlNTLqIX+zS yyjt8jRc/7Ktj4Lb0OiK0ZeOr1yrimrooFGG02XKpOQnaSnFWRtog5ghLdue2xOMAyRD kiUiaU6uJbzkV+Kfw43wg+NtGh2IR9cCnJXIvgf+xHHqNx2D4Hbdk9oDUofTRhwcCVd2 rHiechTm1oR1R5hNtTRwZanqm9yS2vp/Gvy6DSHIguVRQcuIsANBQeSyEN0vbTvBUVws jKn8bDYFPHMJHvr0Y+OUSoq9vDqK41Oc9f2Qf4F2UcYcFR4oIquOipQe5LjGOuwp/DRr S2NQ==
X-Gm-Message-State: AOAM533Hl5118tQLA9BDfALjVfXUwY6IzX7iDEdEnTsLjcRiivHWwjME 0fevk7WQ4ku5p+QWIqqOXHUU2rov5LI2GJlH3ly9vUVT
X-Google-Smtp-Source: ABdhPJyu5iySeyLcSuFJmy8KjF5D6aBNljSNq1Tz89mUULLlJdUxcg+kLXB4/X8mRDG5sFtEtehrGqOO28hwE8bSQMI=
X-Received: by 2002:a9d:75ce:: with SMTP id c14mr631655otl.64.1589395223871; Wed, 13 May 2020 11:40:23 -0700 (PDT)
MIME-Version: 1.0
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <ff2f4862-6e35-84fb-4a63-17b0a7dc917d@cs.tcd.ie>
In-Reply-To: <ff2f4862-6e35-84fb-4a63-17b0a7dc917d@cs.tcd.ie>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 13 May 2020 14:40:13 -0400
Message-ID: <CAMm+LwiNUt2=NU+1MMJBO47y3S0s=hhOVHEJUoWtPoZh-DJZ3Q@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Alissa Cooper <alissa@cooperw.in>, manycouches@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ba084605a58be9b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/S1q2ztw70LBTQ0Hm6u37c4m2MtE>
Subject: Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2020 18:40:26 -0000

On Wed, May 13, 2020 at 1:58 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
FWIW, I'm supportive. I'm also ok with the charter not
> including "should we keep planning 3 f2f meetings per
> year?" but I'd be even happier if that question were
> also included as in scope, perhaps relating to a milestone
> that's scheduled to be discussed only after the initial
> work is done.
>

I am also supportive and have a similar concern. But I can also see why we
don't want to go down that rathole. It is not at all clear to me that we
can have a useful or productive discussion today about a decision we may
never get to take because it ends up being taken for us. I have no idea if
we will meet at all in 2021. It is not just a question of whether we want
to meet, it is a question of whether we are allowed and whether the
economic conditions permit. There is a very real chance that by the time we
are next able to meet, a large number of people who are currently employed
are not.

So what I suggest is that we phrase the question along the lines of setting
out what we can get from different meeting modalities both for IETF
meetings and for interims.

And I would like to see requirements phrased in two different ways. First
in terms of selecting existing products for use. Second in terms of
features we should design in.

The post COVID world is going to be unlike the pre-COVID world in the same
way that WWII was the dividing line for our parent's generation. And if you
read any account of the 'post war' years you will find that the story is
almost invariably begun in 1950 rather than 1945. And thats because the
post war economic boom didn't actually begin the day after VE day or VJ day.

The world is still going to be in crisis even if and when a vaccine is
deployed. And the world is going to be looking at institutions such as ours
to come up with the solutions that are needed to meet that crisis and for
our new way of life.

We are not going to be going back to a world where working in offices is
the norm and work from home the rare exception. Just as WWII forced
employers to accept women into the work force, COVID has forced their hand
on work-from-home.

And we don't have the tools that are needed to really make that work yet.
SMTP remains woefully insecure, the only secure applications we have are
all walled garden models.

We can't build the infrastructure for the post COVID economy on the basis
of proprietary walled garden tech. Even if it succeeds in the short term,
the concentration of power will inevitably be dismantled for the same
reason the anti-Trust laws were passed.