Re: [Gendispatch] Updating the IETF Discussion List Charter (was: Fwd: New Version Notification for draft-eggert-bcp45bis-02.txt)

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 16 July 2021 22:12 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74EB83A0D47 for <gendispatch@ietfa.amsl.com>; Fri, 16 Jul 2021 15:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 9DClqOZtoQmU for <gendispatch@ietfa.amsl.com>; Fri, 16 Jul 2021 15:12:12 -0700 (PDT)
Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com [209.85.219.169]) (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 59DDE3A0D49 for <gendispatch@ietf.org>; Fri, 16 Jul 2021 15:12:12 -0700 (PDT)
Received: by mail-yb1-f169.google.com with SMTP id y38so17254385ybi.1 for <gendispatch@ietf.org>; Fri, 16 Jul 2021 15:12:12 -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=tBr8ueYIgRqK/O3LG04aU6s7J+V9MY+UqwfqJMGpVT8=; b=jcKo8tbK3H3TFmirsk2Cg0g1l7HTdjgBPuGiTO9X19UE4TUVrZISCITYlDgQyfHVGJ yGSjiTOo4rwWz8lvR37YBWm6+qD+CHIm4oCPziSzaSmeoYBKq0DdqlxnehwlmkaxG29v uA88onild+KgAyG9JV2/hvliRz0KOWyMng6J5sMU1/6nPJT4wQiI1g//A+N/gwdZ+ouN A2Jm0zx82NCEx7S+Hoo4hTT/By65Mw5JdyyfjA8T5eKBIYzRWzcYj9epqm/zsgqWWvAy 8Gx3ZXtCO7a9MIQlEufibe+hsNgBtJxYVGrtgcTLaAz5AWaJF2ZdHBdPSh/xcSk9Dvwm ozjQ==
X-Gm-Message-State: AOAM533fFAKKqBGz54PEM4pvOHX5VP4zfrvFvFykGveLhMVt6k6DlGvh VRAZ70NrUcBPybBNEgH/DvUk4dZmOj/xm3euoYddkyusd4KbHw==
X-Google-Smtp-Source: ABdhPJwbxsr2kSNDzPt/MBh291rMXTPlAS7dPDW65tFNj6UO4nDV6lqjQWlDN2b5HOUV/fY6KLMbPhFXBO/5R3bs3Z0=
X-Received: by 2002:a25:2d57:: with SMTP id s23mr15892270ybe.302.1626473531354; Fri, 16 Jul 2021 15:12:11 -0700 (PDT)
MIME-Version: 1.0
References: <162444929705.22096.2956472779291079641@ietfa.amsl.com> <ED2832A3-F392-4F7F-8483-071140AB8FF6@eggert.org> <24DB6859-8538-4A85-8C4C-E35DF688ECB5@mnot.net> <31713928-0cda-4645-0df3-92af3381c2f5@gmail.com> <E1200F2A-6F44-45E7-A0C2-3D953942EBF0@eggert.org> <73ee5ac7-c227-756a-443c-8df6c0308e31@gmail.com> <CABcZeBNDqBuKKa8bPiwyKvG9Zan-edC8NWzk5KhK5PFxWPjXuQ@mail.gmail.com> <F779C816-BFC1-44E7-9137-322CA9F6AB2F@mnot.net> <CAMm+LwhO_hCspkvQbpF4XebQH--Lfpg5WXaAvacpBwNocskqXw@mail.gmail.com> <3a9576e0-d485-6d26-4d6b-3512928e4d6f@network-heretics.com>
In-Reply-To: <3a9576e0-d485-6d26-4d6b-3512928e4d6f@network-heretics.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 16 Jul 2021 18:12:01 -0400
Message-ID: <CAMm+LwjEnr_9pKDTt4nJJeJPpQfUW2X__NuqFOK=oWSs-5u0Pw@mail.gmail.com>
To: Keith Moore <moore@network-heretics.com>
Cc: GENDISPATCH List <gendispatch@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000012b41205c744e1d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/9ztQuG9FA_pGeyOww8Oq0Zy8WQo>
Subject: Re: [Gendispatch] Updating the IETF Discussion List Charter (was: Fwd: New Version Notification for draft-eggert-bcp45bis-02.txt)
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2021 22:12:18 -0000

On Fri, Jul 16, 2021 at 4:53 PM Keith Moore <moore@network-heretics.com>
wrote:

> On 7/12/21 8:02 PM, Phillip Hallam-Baker wrote:
>
> On Mon, Jul 12, 2021 at 7:21 PM Mark Nottingham <mnot@mnot.net> wrote:
>
>> Somewhat relevant, courtesy of the newsclips service:
>>   https://www.nytimes.com/2021/07/10/business/gen-z-email.html
>
>
> Every single time someone suggests there is a user demand for something
> better than SMTP email from the 1980s that hasn't changed since MIME, they
> are aggressively patronized and told that there is absolutely no way that
> the legacy system can ever, ever be replaced.
>
> On the contrary, email is constantly being replaced with facilities that
> are far less functional.     As far as I can tell, the biggest problem with
> email is that has become so widely used by everybody and everybot, that
> one's mailbox is typically full of low-value information.  (And while the
> delete key is not hard to find, there are so many low-value messages that
> simply selecting and deleting messages is a time-consuming chore, and every
> low-value message is a nuisance.   Also, not everyone deletes messages as
> they are read.)
>
The critical flaw in all the mail alternatives is that make them less than
SMTP is that they are closed. Can't use Signal to call a Skype account.
Everyone has their walled garden, and none of the majors see any reason to
open their proprietary systems up.

But we need to go further, email is also defective as a change of mail
service provider forces me to change my email address unless I own a DNS
domain which is far more than most people on the planet can afford. (No
redirects do not solve this problem as I have to rely on the old service
provider to redirect).

And of course, end to end encryption, digitally authenticate every message
and zero effort security are table stakes.


We need a mail system that allows a user to use their human friendly name
for life. So @alice, not alice@example.com. And that name has to be really
cheap and owned by the user, not rented with an annual fee.

This is not yet operational but I think it could fit the bill:

Mathematical Mesh 3.0 Part VII: Mesh Callsign Service (ietf.org)
<https://www.ietf.org/archive/id/draft-hallambaker-mesh-callsign-00.html>
https://www.ietf.org/archive/id/draft-hallambaker-mesh-callsign-00.html

This architecture is targeted at personal use. DNS works OK for
organizations which is what it was designed for.


Basically it is a blockchain approach without any crypto-currency ideology
involved. The registry binds a name to a public signature key which is the
user's root of trust and the address of their current service provider.

The registry is public so you are not going to want to put an SMTP email
there unless you are a masochist. But the service provider can publish
(under suitable access control) a contact record giving SMTP, Jabber,
OpenPGP, S/MIME etc. coordinates.


Maybe there isn't interest, after all, on day 1 the only use for a
messaging scheme of this type is going to be inside organizations. But that
is where at least 80% of communication is occurring in most enterprises.
Having a separate secure email system for internal use does make sense. And
especially if it then allows communications with the lawyers, accountants,
customers, etc.