Re: document writing/editing tools used by IETF

Phillip Hallam-Baker <phill@hallambaker.com> Sat, 27 February 2021 19:54 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 A9B963A132D for <ietf@ietfa.amsl.com>; Sat, 27 Feb 2021 11:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 46MSLp_BKzh7 for <ietf@ietfa.amsl.com>; Sat, 27 Feb 2021 11:54:13 -0800 (PST)
Received: from mail-yb1-f174.google.com (mail-yb1-f174.google.com [209.85.219.174]) (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 210BD3A1326 for <ietf@ietf.org>; Sat, 27 Feb 2021 11:54:13 -0800 (PST)
Received: by mail-yb1-f174.google.com with SMTP id p193so12600398yba.4 for <ietf@ietf.org>; Sat, 27 Feb 2021 11:54:13 -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=1xohKfM1yhrUgxjnwI6XTo4ETTNx2ugjEoh6B14ZQQg=; b=V66Nh97dSMyPtWPUqQjAriAm10dal9viMOcBWzIL+a++0u23D6fopWtTJzs5doXC+P L3dYSXSwPRUa4/sHdoXyQCIKKqnOBfELZOS63YXrumkA8ZciaKljnQecgYBwMWUIJuZX yOj1go3RPi7xxz/zv6/z+rAZg7lX0mTNSbiy6kbp2FIUq3jXDmk3/Ixm+pdfpBF+aSg3 OZTOfiTJ1IQvzCYWa5Z3+/Bqca9tGiHkj55x87Lgw6R1BzyonFilID8CuvruoOThYKZt 6So4oVKhe/T0qaYrMPoiIqnLWV9/5GXkj9e5b57nK0GJnQ6McLxFD+b23UQJFWpZbrbu FT9g==
X-Gm-Message-State: AOAM5316iytZbyHbBW3xrFjuA8s7nVM4PCnAuHGy34pDNzaudxHBeNLH IWdS/cw+BnF+tINPa7RKja4OlaEsRD7yzWKGPAw28pE85Cg=
X-Google-Smtp-Source: ABdhPJyXySiHvqUpNRivZOjRSm6JLE1aPRsxSwDHxVDWALIhFQU+D3MX2rZRGoBDkaB+a+rpwlfJVs8Nl+fFvw08Q0A=
X-Received: by 2002:a25:ad67:: with SMTP id l39mr13246629ybe.172.1614455652276; Sat, 27 Feb 2021 11:54:12 -0800 (PST)
MIME-Version: 1.0
References: <CAMm+LwhOqy2MCmAY5eO2OcpkM99UOS7A5hJaj+thA3SuO+g8FA@mail.gmail.com> <20210227190200.06ED46F10439@ary.qy>
In-Reply-To: <20210227190200.06ED46F10439@ary.qy>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 27 Feb 2021 14:54:02 -0500
Message-ID: <CAMm+LwjStMkDti9uj+QbFA_pT3zc33b0=T-aVwtBeUO9PJXPgg@mail.gmail.com>
Subject: Re: document writing/editing tools used by IETF
To: John Levine <johnl@taugh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8de8805bc56bfb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f8flvmykR_wJ6bNKF9KKxVogiBg>
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: Sat, 27 Feb 2021 19:54:15 -0000

On Sat, Feb 27, 2021 at 2:02 PM John Levine <johnl@taugh.com> wrote:

> In article <
> CAMm+LwhOqy2MCmAY5eO2OcpkM99UOS7A5hJaj+thA3SuO+g8FA@mail.gmail.com> you
> write:
> >Previous attempts to get a discussion going on what tool we would want...
> >haven't exactly been successful. They turn into a github vs mailing list
> >editor war when my interest is quite different.
>
> I agree that neither mailing lists nor github are ideal for the way the
> IETF works
> today but I would be very unhappy if we invented yet another bespoke
> locally maintained
> bunch of software.
>
> We're strange but it's hard to imagine that we're so strange that there
> isn't an
> existing package somewhere that will do the job either as is or with minor
> customization.
>

My plan is not to develop a niche tool for the IETF.

At this point I have a Threshold Key Infrastructure that enables a cloud
service to control decryption of data that the service cannot decrypt
itself. That is all open specifications, open source code and can use
either the ICANN DNS or the Mesh callsign registry to provide open
discovery. The code is very nearly complete.

As I said in a recent conference call, I am not a communist. I know that
the commercial potential of this work is significant. I am mostly doing
this because I want something to do but I wouldn't mind a Turing award and
I certainly wouldn't mind more loot.

I have designed my TKI so that it has the potential to add value to
products in many different industry sectors. Of course, most people in the
industry will ignore the ideas until there is a commercial threat to their
business. That happened with the Web as well. It was only after the White
House adopted the Web that the dotcom boom really started and every CEO was
suddenly asking if they should have a corporate Web site.

Since nobody buys raw technology, I am going to need an application that
provides an effective demonstration of the potential. And a collaboration
tool in which all the data is encrypted, including in the cloud is one of
the technology demonstrations that is probably the easiest to get venture
capital funding for.