Re: A different approach to remote meetings / Mesh videos

Yoav Nir <ynir.ietf@gmail.com> Sun, 13 October 2019 05:23 UTC

Return-Path: <ynir.ietf@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 61F9B1200D6 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2019 22:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 vJEpcCS6lo5c for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2019 22:23:44 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 4DDC5120025 for <ietf@ietf.org>; Sat, 12 Oct 2019 22:23:44 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id r4so12024497edy.4 for <ietf@ietf.org>; Sat, 12 Oct 2019 22:23:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YoZ3ZJNE2aIfMAZ79gaG6W5IuhmdFx/KN9jLygRT2rc=; b=rIzGLIoEuclLLRkutCNOJ0v9sTh5mhdowW2Wc+d0aE1hTUm5Qw816NoSjPQh7vIz3N vztHJ5DQ1qsnvv02bjjrgl/aqmLogYKmhglQqpeKiuoyN3N2dAWn+eMua2BDpsSbWcuj L0WnB4kXfujZIzNAov8OE3zFsljyb3RS6n4YUWwqoUdWQJ8UDd3iT22En6ii/8dOqDqC sHrteiSodZZ/Mu4QfwbF/IbY9ur/Rm8ZuHim6P4LvN/Ff/NLGDuEiivl6QuIkxerBsRA 5AwUOm6T6XnLcfwQSXOcuOIDSJmv6KjDZE61SMxOhXQdl4AQ/tHjawALlBo/zp4azNvl /e/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YoZ3ZJNE2aIfMAZ79gaG6W5IuhmdFx/KN9jLygRT2rc=; b=srqENNfbFwCl5t3IuwFQ6ERyDg7dAoSMN66xpi5kbWU0P8uuZxFWDSN1qMDwPMICv7 UAKyd6KUhHDMFausAN4GU1/z04vO9pnq9HL3PuhDOc5E8mD2eBwH6qWCd4f81TXPJM9N YD5HOWVuhhPeEeyFxl93aITa6uJOz3dNekGEO/6pC5yFGG5ng1kOtwGUBcjjvxDKHMv2 UdaHre4licTmwE+epHXVN0rOG34uT5jCuwuybs9Dk5MS8XccqnMnswpJ32wp3XyRVwqr 2lVtrLpfDDQpXv0CZxmwXD/3MINGm3sqmmzHvIYviw+HHuQExllsN7d76bDcElONPqHe H1NA==
X-Gm-Message-State: APjAAAVUAj6Ib4OiOJsZYZq6MfNTC+QYE4Qcuan6eABqgVxtefZck/uX e7WHWiA7LukJ7P8sbafq9aiaI1+y
X-Google-Smtp-Source: APXvYqy2u+gZWgJOkBg1v9KhQJXQ1NdFGcDJhmrpS4XjSh3ChhcRBoL6W4MzuTV/QBu4Y79WCbEZdQ==
X-Received: by 2002:aa7:d756:: with SMTP id a22mr22230964eds.198.1570944222851; Sat, 12 Oct 2019 22:23:42 -0700 (PDT)
Received: from [192.168.1.12] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id nq1sm1795023ejb.75.2019.10.12.22.23.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 12 Oct 2019 22:23:41 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <A144E7BD-2ECC-4D6B-B7CB-110F22B688B1@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3AACDFCC-A898-40CD-9E57-0E1AED71821E"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
Subject: Re: A different approach to remote meetings / Mesh videos
Date: Sun, 13 Oct 2019 08:23:36 +0300
In-Reply-To: <CAMm+LwjokhxkJXdPczfHQVWqMG1x528yXZ=vvu4yq1W3R9T=YQ@mail.gmail.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <CAMm+LwjokhxkJXdPczfHQVWqMG1x528yXZ=vvu4yq1W3R9T=YQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fWfGZ2fl3d4-LBizOouUzVMBTfM>
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: Sun, 13 Oct 2019 05:23:47 -0000

So “Who here has read the drafts” will be replaced by “Who here has watched the videos” ?

Phil, you are really good at public speaking. You make compelling and entertaining videos. Most of us are not able to make videos that good. Additionally, videos are far less interactive than a presentation unless you expect the technical discussion to happen on the youtube comments. Which it totally shouldn’t.

And then there’s the effect of the technical discussion. It’s fairly easy to update slides or drafts. If the group has decided to ditch CBOR in favor of DER, that’s fixing a slide or two plus a paragraph in the draft. The video, you’d probably need to reshoot several minutes of it if you’re good at planning and editing videos, or reshoot the whole thing if you’re not.

While I see the utility of making videos for tutorials, introductions and the like, I don’t see how it meshes (pun intended) with the whole standards-making process.

Yoav

> On 13 Oct 2019, at 7:33, Phillip Hallam-Baker <phill@hallambaker.com> wrote:
> 
> The IETF has not changed its meeting format since I attended IETF 34 in Dallas back in 1995. We have developed much remote presence technology since. Surely we should start using it.
> 
> Do we really need to meet in plenary session three times a year? Is the model where IETF meeting time is limited to brief status updates and most of the work is 'taken to the list' optimal ?
> 
> Maybe we need to change our existing model or maybe we need to keep it unchanged and supplement it somehow. Remote meeting attendance is better than nothing. But does it really help for me to wake up at 2am to listen to a complex technical talk? Perhaps all meeting at the same time has to be rethought, not just meeting in the same place.
> 
> Perhaps what we could do is to move some of the technical content out of the meetings altogether and put it up on the Web. To test this theory and also to promote my efforts to make computers easier to use by making them more secure, I have begun filming a series of videos explaining the Mesh technology. These are currently available through the links below and I will work out some way to distribute the material in a downloadable format (2k/4K) so people can take them for 'in flight entertainment' on that 24 hour flight to Singapore.
> 
> The channel is here:
> https://www.youtube.com/channel/UCaWFcKKJOO8KBzvlbdHtK8Q <https://www.youtube.com/channel/UCaWFcKKJOO8KBzvlbdHtK8Q> 
> 
> The material itself is currently unlisted but can be accessed directly from the links below. 
> 
> For the purposes of this experiment, the four videos have very different material:
> 
> Mesh 1: The Mesh at 10,000 ft, explains the requirements the project is designed to address without drilling down into the technical details. It is the sort of pitch I give to potential investors / stakeholders.
> https://youtu.be/pPuV1Wz3CIY <https://youtu.be/pPuV1Wz3CIY>
> 
> Mesh 2: The Devil is in the Deployment, is not technical at all. It is explaining just why I think a proposal of this scope it entirely feasible and describes the strategies I copied from Tim Berners-Lee to get it deployed.
> https://youtu.be/mUoFtxWc28w <https://youtu.be/mUoFtxWc28w>
> 
> Mesh 3: How the Mesh works, is a more technical overview of how the various parts of the Mesh are designed to work together.  The sort of thing an IAB plenary tech talk might be. Technical knowledge is assumed but not deep understanding.
> https://youtu.be/mv2edt7HT4g <https://youtu.be/mv2edt7HT4g>
> 
> Mesh 4: Meta-cryptography for key splitting is a graduate level technical presentation giving material that is not in the cryptography textbooks (yet). The sort of presentation I might give at MIT CSAIL etc. 
> https://youtu.be/zY7ygPnpDzk <https://youtu.be/zY7ygPnpDzk>
> 
> Given the IETF preference for a minimalist approach to presentation, there are no PowerPoint slides at all.
> 
> The remaining videos will be posted as they are completed, these will include technical drill downs on each of the three technologies I am proposing and an explanation of how we can then apply the Mesh to create novel and interesting security solutions for the Web, SSH, OpenPGP, S/MIME etc.
> 
> The videos will be going out to the public shortly. They are all Creative Commons with attribution