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

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 26 February 2020 22:03 UTC

Return-Path: <hallam@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 3FBDE3A0890 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 14:03:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 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_H2=-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 fufLuUKawmvE for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2020 14:03:36 -0800 (PST)
Received: from mail-oi1-f181.google.com (mail-oi1-f181.google.com [209.85.167.181]) (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 32F9E3A08A5 for <ietf@ietf.org>; Wed, 26 Feb 2020 14:03:36 -0800 (PST)
Received: by mail-oi1-f181.google.com with SMTP id q84so1189474oic.4 for <ietf@ietf.org>; Wed, 26 Feb 2020 14:03:36 -0800 (PST)
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=a1kCOq3zyAgT/qsk7VYS3P3xXVewez901UBnbCkWrUs=; b=PmRMWI3wGJSXjJnMvTBk/KMLs3RtOUuxQwbzWKb8on5DOk25FBXYGuIgvXkrRs2ELS cDCpatfD6t4LHEr1s2qwr3ugxcn7YdVpA6OX7aom8j5Ut1mQNB9YPiaIANzoSpLza4I7 fQo1Kro0I/UyjMqRtC5/H5ntJPWPPJ7/xCFlp0xcpJsv+ALaqC/CnxLqqzliJl2aBQN4 zbFsPYad5pXbBnnUSk4/GdKw9IcCxpq474GhQuLXyTURjwMwSUhlYppL0+f7krBSsMsD 9ebTuk9IuRB0sdIbFruDw/OmfWZRLMklBqOXt9PIl0y8wOQZVkr/qiYPS3a2Eg2XqCEW 4yPA==
X-Gm-Message-State: APjAAAWyBxLyHcA7subp8kI0zxLQLZEIw8XjGY9QKakYGYnwXYNgBkP7 4Ko/zfCUl9p1HRLKDgGMQvubfrSGSRGMIQzO2yE=
X-Google-Smtp-Source: APXvYqw+EVoZpZ3bRslMB8u0iZsicZ9OFyk2sKD/sQycPKwUUcFaNr+UosEg0W+amBFVQkh1bEAEccBv+76OBwnLybo=
X-Received: by 2002:aca:cf94:: with SMTP id f142mr905070oig.31.1582754614811; Wed, 26 Feb 2020 14:03:34 -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> <CAMm+LwjLzP5bA56mPV0OxdBV=hWKCaD8DN7bqJ0gipq67-iwpw@mail.gmail.com> <2e8208f7-1a67-2baa-8685-71bf33f029e4@joelhalpern.com> <CAMm+LwjM6nJwu2XKwCdcBCWa=vP-Y5w2v6xNZupMpf_k65cM4w@mail.gmail.com> <89b8ebec-3abe-e7b4-e856-2de851731735@foobar.org> <CAAuWHCKZEbDKmKWzhgFuDaBVZMtDAGfNktPvZTzU8fp9Cr8NkA@mail.gmail.com> <CC7D4D98-5FE8-4F59-8CC6-63E8872EE8FD@ietf.org> <f4af3a15-570f-a595-2d17-896a6db62173@network-heretics.com> <CAL02cgTUCS_WMsYYqE32wz5DWNyosBOR7W_ygsi4bOoY3F+-jQ@mail.gmail.com> <2088d7e7-34c1-ab7b-59c6-b8fe3ce5607d@gmail.com>
In-Reply-To: <2088d7e7-34c1-ab7b-59c6-b8fe3ce5607d@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 26 Feb 2020 17:03:23 -0500
Message-ID: <CAMm+Lwgc8NRg8E-DeqCZW=re+LerVpnaG94LWY87mY3gB7o3Vg@mail.gmail.com>
Subject: Re: What can IETF do? Re: Further update on COVID-19
To: Melinda Shore <melinda.shore@gmail.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009521f0059f81c60b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jMx_L6KavXM31W7c5WHCCHH1uP0>
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 22:03:44 -0000

On Wed, Feb 26, 2020 at 4:13 PM Melinda Shore <melinda.shore@gmail.com>
wrote:

> On 2/26/20 12:08 PM, Richard Barnes wrote:
> > https://secondlife.com/
> >
> > ISTR the IESG had a meeting there once a few years ago.
>
> Netroots Nation had a couple of conferences gatewayed into
> Second Life.  It wasn't terrible, and that was over a decade
> ago.  Might be worth experimenting with again.
>

I could use an avatar at this point. It is somewhat ironic that I am
proposing this stuff when I can't do remote either. I can type and I can
read and I can think and thats about it. Anyway, this is the system I have
had in mind for quite a long time and is the reason I have built (and had
others build for me) some of the stuff I have in the past year.

I am a systems guy, this is not just about conferences, its about the
system.


First, lets start with Internet Drafts. I have written my own
document handler taking Markdown and Word as inputs and generating XML2RFC
as an output format.

The second half of that system is the comment forum. So the draft is
uploaded to some service. You can read through the draft and click the
pilcrow on any paragraph and a comment dialog opens up. This asks for:

1) Lightweight semantic: Agree/Disagree/Clarify/Object
2) Explanation (some text).

For IETF purposes, we don't need end-to-end security. But if we were going
to use this to provide group collaboration on bidding on RFPs or the drafts
of the quarterly SEC reports, we need that and I have designed the tools to
make that possible.

Entering a comment creates an object which has its own lifecycle. Basically
a comment is an issue and these should eventually get cleared. So when a
new version of the draft is uploaded, the editor checks off which comments
have been cleared.

So that is the sort of thing I want to replace mailing lists with. I want
the drafts to serve as the reference point for the discussion.


So now, let us imagine that an issue is raised that is more complex than
can be disposed of by a comment. Something like the discussion we are
having now. Well that is the point at which I would like to be able to set
up an ad-hoc virtual meeting to discuss that particular point. So lets say
we have a bunch of issues raised on the splunge topic:

1) Someone proposes a virtual meeting.
2) (optional) WG Chair, Editor approves.
3) Negotiation of date, time, agenda
4) Have meeting
5) Report back result

Point here is that while we talk about 'consensus', that is rarely the
relevant test. Quite often, the relevant test is 'is there a major security
hole if we do things this way' or 'what are the interop concerns'.

The type of capabilities that are relevant to a meeting of that type are
likely to be:

1) Voice
2) Screen sharing (for slides, demos, etc.)
3) Video
4) Whiteboard input (i.e. iPad + pencil or Microsoft Surface type
interaction)
5) Transcription (voice to text).

Oh and yes, we want all this on the record and to save every byte for IETF
and for Enterprise. But I can also provide an OTR version of the security
protocols.

We need to have some sort of concept of process rules. Not necessarily
Roberts Rules. But maybe everyone in the meeting starts with ten minutes to
talk and that counts down when they hold the floor. And maybe if someone is
saying something interesting people can pass some of their time to them.
And maybe we have thumbnails of everyone apart from the person with the
floor who gets full screen treatment.


So this is not quite hallway discussion but it is close. Some hallway
discussions fit into this pattern. When I go to an IETF, I know that I have
a list of folk I want to raise very specific issues with. But the other
part of it is 'serendipity'. I am not quite sure how to incorporate that
into the model yet.

One option would be a sort of Facebook like feed with some sort of curation
process that results in proposals to hold meetups or discussions. Or maybe
we have a model in which there is a large public concourse and people who
are interested go off to private meetings.


PHB