Re: [saag] post-X509 cryptographic identities

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 11 February 2020 21:39 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5210B12081C for <saag@ietfa.amsl.com>; Tue, 11 Feb 2020 13:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 ckCjZ7cCYVSr for <saag@ietfa.amsl.com>; Tue, 11 Feb 2020 13:39:44 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF251120018 for <saag@ietf.org>; Tue, 11 Feb 2020 13:39:43 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [46.183.103.8]) by relay.sandelman.ca (Postfix) with ESMTPS id C045E1F459; Tue, 11 Feb 2020 21:39:41 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 25B131A26A6; Tue, 11 Feb 2020 22:39:25 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Derek Atkins <derek@ihtfp.com>
cc: saag@ietf.org
In-reply-to: <a8435b3674ac1a98820e7dd653725613.squirrel@mail2.ihtfp.org>
References: <157762745765.1150.7880025422884493076@ietfa.amsl.com> <2C5DFA70-AD0E-4139-B28E-2D4EDB6E5409@sinodun.com> <46BDE9EB-6306-4194-AFFA-7E9E6604765F@sinodun.com> <825b8c8e-7ee9-9276-d09e-9c006acf3804@ericsson.com> <CABcZeBOzJ2MRS8deZqN+e-o9tFDwgSrYK3_hmV-0pfO+L9oaVw@mail.gmail.com> <53c87d6b-cad1-3a80-291d-e2a896705da5@ericsson.com> <CABcZeBNJWmFTV==6sa0qnAPyRr4=6OiCacchzobE=RozHnqPdg@mail.gmail.com> <7901248e-c7dd-8a12-65df-f40415fde5e2@cs.tcd.ie> <26497.1581418516@dooku> <8ccb201a00d4e693c882225170ca424f.squirrel@mail2.ihtfp.org> <3643.1581431204@dooku> <a8435b3674ac1a98820e7dd653725613.squirrel@mail2.ihtfp.org>
Comments: In-reply-to "Derek Atkins" <derek@ihtfp.com> message dated "Tue, 11 Feb 2020 09:40:27 -0500."
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.2.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 11 Feb 2020 22:39:25 +0100
Message-ID: <4232.1581457165@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/DlFC3Y_8km7QxDk0CbTntC2P04I>
Subject: Re: [saag] post-X509 cryptographic identities
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 21:39:47 -0000

Derek Atkins <derek@ihtfp.com> wrote:
    > My personal opinion is that it was neither a technical issue nor an
    > implementation issue that caused the market to choose X509 vs OpenPGP, but
    > rather a philosophical issue (or perhaps business-money-making
    > choices).

I'm not actually trying suggesting that they served the same purpose.
X509 encrypted email (SMIME) is astonishingly rare, despite hundreds of
millions being spent within Governments deploying things.  It's important to
understand if there were technical decisions that resulted in market failures.

    > On the other hand, if we're going to rehash the design requirements for
    > X.509, I think it makes sense to also rehash the differences in
    > requirements for SPKI and OpenPGP (and maybe even DNSSec).  Specifically,
    > it's important to discuss how they differed, but also in what ways they
    > overlapped.  I do agree we don't need to go into the full history of all
    > of them (including X.509).

What I want to understand is: are we living with technical decisions that
made sense at the time, but which are now resulting in pain?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-