Re: [saag] post-X509 cryptographic identities

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 18 February 2020 12:54 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 5242F120098 for <saag@ietfa.amsl.com>; Tue, 18 Feb 2020 04:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 s_aUhky58jVp for <saag@ietfa.amsl.com>; Tue, 18 Feb 2020 04:54:14 -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 D9A1A1200A4 for <saag@ietf.org>; Tue, 18 Feb 2020 04:54:13 -0800 (PST)
Received: from dooku.sandelman.ca (client-141-23-178-142.wlan.tu-berlin.de [141.23.178.142]) by relay.sandelman.ca (Postfix) with ESMTPS id E82A11F486; Tue, 18 Feb 2020 12:54:11 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 457741A2BE4; Tue, 18 Feb 2020 11:07:57 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tony Finch <dot@dotat.at>
cc: saag@ietf.org
In-reply-to: <alpine.DEB.2.20.2002172037090.12712@grey.csi.cam.ac.uk>
References: <ac360994-e747-6913-fdc3-19b7db2e00c3@netmagic.com> <3854.1581431519@dooku> <20200213174617.GQ18021@localhost> <18044.1581688781@dooku> <20200214203306.GW18021@localhost> <3586.1581771453@dooku> <20200215184827.GB18021@localhost> <3459.1581938558@dooku> <20200217155412.GC18021@localhost> <20200217160522.GN49778@straasha.imrryr.org> <alpine.DEB.2.20.2002172037090.12712@grey.csi.cam.ac.uk>
Comments: In-reply-to Tony Finch <dot@dotat.at> message dated "Mon, 17 Feb 2020 20:48:45 +0000."
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, 18 Feb 2020 11:07:57 +0100
Message-ID: <25018.1582020477@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/F0Rx2ZwRGgIdyZLJ4zRuKjRjLqk>
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, 18 Feb 2020 12:54:17 -0000

Tony Finch <dot@dotat.at> wrote:
    >> On Mon, Feb 17, 2020 at 09:54:13AM -0600, Nico Williams wrote:
    >> 
    >> > DNS/DNSSEC almost by definition cannot provide a solution for >
    >> smaller-than-universal namespaces,
    >> 
    >> That's may not be exactly the case (haven't read most of the thread,
    >> so perhaps missed something important posted before).
    >> 
    >> Your last hop (or stub) resolver can be configured with whatever
    >> trust-anchors you want for suitable private branches of the namespace.

    > I had something vaguely SKPI-flavoured in mind when I wrote
    > https://mailarchive.ietf.org/arch/msg/saag/jlVNCTQxyhLRjBLYLl9V0Wk_UKI

    > And also something related to the notion of "petnames" for capabilities
    > as a way to tame Zooko's triangle
    > http://www.erights.org/elib/capability/pnml.html

I am very enthusiastic about PetNames.

    > Interesting things happen when you combine SPKI-style path names with
    > petnames as local roots, especially for IOT and MANET
    > applications. When I create a secure association with a device, I give
    > it a petname which is my personal human-readable stand-in for its
    > public key. And it I want to share some devices with a friend, they
    > don't have to import a petname per device, they can just link to my
    > root.

I am completely onboard here.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [