Re: the introduction problem, was Email and reputation (was Re: Service outages planned for April 25)

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 15 May 2022 03:20 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 E54C2C183537 for <ietf@ietfa.amsl.com>; Sat, 14 May 2022 20:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level:
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJdfEI2ScsdD for <ietf@ietfa.amsl.com>; Sat, 14 May 2022 20:20:35 -0700 (PDT)
Received: from mail-yb1-f180.google.com (mail-yb1-f180.google.com [209.85.219.180]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56C10C183538 for <ietf@ietf.org>; Sat, 14 May 2022 20:20:35 -0700 (PDT)
Received: by mail-yb1-f180.google.com with SMTP id r1so21665213ybo.7 for <ietf@ietf.org>; Sat, 14 May 2022 20:20:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fqzsm7CbsXJ+NElUordDcOELncf6luC+uffi7qPnZ7o=; b=u+7hSZrJzUrpKU7MR/BQnSiCkL1eMT4ORfphcPAS5RtUUzHcD16SWHl2eBl8aGZHPe Ci1ho7oBUkRyDB5rXYXN7EIFQT3QTYhu7LMRBC0e2Zta/D3mRoGtgI9OeDYVKrd2Dn/L YlxwGJA2/0IKjj9RASKAyk5y5huj3+Fy3tSz8bmnNcNkRXiqi2tO+WvKMsoBbHCyVSCj bV8okdHouP0ZM+0Q0y+QcyLkScErPX+plK/AUrvjO1F0VJhSUrlKI+Izy3KfskgUuDix g8o9Z0t7g/NSMTjeln4AFsifIXtpRhS050ukpxcuEHX/i1zGFjEyGpI1jKtSIJRmVOsg 0UAA==
X-Gm-Message-State: AOAM531mHdtE0rQ3ee3/Y1fxJSeZgbwfQB4JOyRusMXdm6RpyJRDkDAE gTWpQ9zi2ry4ioBFZqUWZQsUcX9Acx5N3Cg9/CANyyTG
X-Google-Smtp-Source: ABdhPJxqn23JVa80B+oo2zxU/CIpXuHzBXTty2Nn1g9OhQM2406XXN9rhoTEQ+wcPOckjjaffNVFhWsLgGSvGhXlitM=
X-Received: by 2002:a25:2406:0:b0:64c:70a0:af75 with SMTP id k6-20020a252406000000b0064c70a0af75mr7503582ybk.456.1652584834471; Sat, 14 May 2022 20:20:34 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwhD8wHJ284z91X5XP-8f+9=Dx1Kd50=8-Pd3SX==W6ivw@mail.gmail.com> <20220514171447.23A3840334EA@ary.qy> <CAMm+LwivypwPG_mAc=3w=dY4w9rgvO8+qY=c3Et+Gkitdw8GMA@mail.gmail.com> <3a66b3f8-03c0-d6b4-51fc-df093d88524f@taugh.com>
In-Reply-To: <3a66b3f8-03c0-d6b4-51fc-df093d88524f@taugh.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 14 May 2022 23:20:23 -0400
Message-ID: <CAMm+LwjddEN3zS76SCnNtRb1cvq3ofnDdy6YXP5-SqjEsf2-8Q@mail.gmail.com>
Subject: Re: the introduction problem, was Email and reputation (was Re: Service outages planned for April 25)
To: John R Levine <johnl@taugh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000051dbf05df046430"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FWLszUZ-BwZ8FV0YGkuGoRd59VM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
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, 15 May 2022 03:20:36 -0000

On Sat, May 14, 2022 at 9:32 PM John R Levine <johnl@taugh.com> wrote:

> > My goal is to sufficiently solve the problem so that I spend a negligible
> > amount of time dealing with unwanted communications.
> >
> > You keep setting up this binary success/failure.
>
> No, really, I'm not.  We've been looking at the online introduction
> problem for decades, and the real life introduction problem for millenia.
> Everything you propose has been tried before.  Much of it sort of works,
> sometimes, but none of it well enough that it's worth a large upheaval to
> use.
>

Everything in the iPhone had been tried before. Every single thing.

Everything in the Web had been tried before.

It is not just the raw technology, it is having the complete package. Or at
least enough of the complete package that people can imagine the gaps being
filled. In particular, the ability to provision private keys into devices
as a one-time operation that never needs to be repeated is something we
never had in the past. The ability to revoke private keys themselves and
not just the credential bound to the keys are game changers.



--
PHB