Re: What can IETF do? Re: Further update on COVID-19

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 26 February 2020 17:36 UTC

Return-Path: <jmh@joelhalpern.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 B211B3A0E5C for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 09:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 wQ__ZrhxIYNR for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 09:36:58 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A06B93A0E54 for <ietf@ietf.org>; Wed, 26 Feb 2020 09:36:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 48SNK645wLz1p0qX; Wed, 26 Feb 2020 09:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1582738618; bh=5ntLNFBWfrfRo9UohHDCc+d6lOUxC/HLNr46rDYAw0c=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=k5nxJp+NIR71tnXiZ+sTrMmeY/x9QxqrwjR86+wsineEsKS5O9iwFA7i79LIHXS2I JafK6sWhTgzdv+8zjGYMoW+8mxpQw2MLjFSiM9ssr2w13FZnH+brfyA+tdmxcdnmy+ ujrjjkkpQdVxlz56eDKgP671m8ZJ8vA2QG3OaA+8=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.47.231.45] (unknown [213.50.241.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 48SNK555xRz1p0H5; Wed, 26 Feb 2020 09:36:57 -0800 (PST)
Subject: Re: What can IETF do? Re: Further update on COVID-19
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF <ietf@ietf.org>
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> <CAMm+LwjLzP5bA56mPV0OxdBV=hWKCaD8DN7bqJ0gipq67-iwpw@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <2e8208f7-1a67-2baa-8685-71bf33f029e4@joelhalpern.com>
Date: Wed, 26 Feb 2020 12:36:54 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjLzP5bA56mPV0OxdBV=hWKCaD8DN7bqJ0gipq67-iwpw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z0l5YYHyEE4TSEHAZXSJ8MvCDXY>
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: Wed, 26 Feb 2020 17:37:00 -0000

Actually, I doubt very much that we have all the pieces to have virtual 
meetings that are as effective / useful / ... as face-to-face meetings.

I would not be surprised if we have all the tools to have useful virtual 
meetings for those cases when we can not or do not wish to have 
face-to-face meetings.
But we should also remember that assembling systemic solutions from the 
protocol parts is a different skill from the set the IETF tends to look 
for and use from its participants.  So it is not obvious how we get from 
here to there.

Yours,
Joel

On 2/26/2020 12:31 PM, Phillip Hallam-Baker wrote:
> It is probably too late to get things together in time to have an impact 
> on COVID19. But let me remind everyone of what we are supposed to be:
> 
> An engineering organization that produces standards that allow people to 
> communicate.
> 
> This is the second time we have had a major fear of a pandemic in a 
> decade. There is a clear need to be able to hold really really good 
> virtual meetings and the technology is still not up to that.
> 
> I am pretty sure we have all the pieces at this point but we don't have 
> them integrated into a system. We have QUIC, adaptable video and audio 
> compression already. I have shown how we can adapt existing crypto to 
> provide end-to-end encryption. My colleagues Mallory and Hurwitz 
> demonstrated the lightweight semantics required to keep large meetings 
> (e.g. Al Gore's open meeting of 2,000 people) functioning.
> 
> What we need to do is to integrate these.
> 
> If there are people interested in working on that, lets get started.
>