Re: [Din] WSJ article on Identity and Blockchains

David Mazieres <dm-list-ietf-ilc@scs.stanford.edu> Wed, 11 April 2018 00:04 UTC

Return-Path: <dm-list-ietf-ilc@scs.stanford.edu>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96FD12D876 for <din@ietfa.amsl.com>; Tue, 10 Apr 2018 17:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9fe8fVPFJmF8 for <din@ietfa.amsl.com>; Tue, 10 Apr 2018 17:04:55 -0700 (PDT)
Received: from market.scs.stanford.edu (www.scs.stanford.edu [IPv6:2001:470:806d:1::9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5835012D944 for <din@irtf.org>; Tue, 10 Apr 2018 17:04:55 -0700 (PDT)
Received: from market.scs.stanford.edu (localhost [127.0.0.1]) by market.scs.stanford.edu (8.15.2/8.15.2) with ESMTP id w3B04nF5033642; Tue, 10 Apr 2018 17:04:49 -0700 (PDT)
Received: (from dm@localhost) by market.scs.stanford.edu (8.15.2/8.15.2/Submit) id w3B04nrX040743; Tue, 10 Apr 2018 17:04:49 -0700 (PDT)
From: David Mazieres <dm-list-ietf-ilc@scs.stanford.edu>
To: Thomas Hardjono <hardjono@mit.edu>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "din@irtf.org" <din@irtf.org>
In-Reply-To: <5E393DF26B791A428E5F003BB6C5342AE7404E4C@OC11EXPO33.exchange.mit.edu>
References: <5E393DF26B791A428E5F003BB6C5342AE73F70FC@OC11EXPO33.exchange.mit.edu> <E1f57in-0004gH-Gx@mta0.cl.cam.ac.uk> <CAPaG1Amqd8DehMpvht8zEPzqHg00wqYcUDXb0g-bQebTvbXWzw@mail.gmail.com> <fb88b314-c402-7f39-79ea-01c46fdf16ec@gmail.com> <5E393DF26B791A428E5F003BB6C5342AE7404E4C@OC11EXPO33.exchange.mit.edu>
Reply-To: David Mazieres expires 2018-07-09 PDT <mazieres-aty9ij5833stt63zi94a3ei2hi@temporary-address.scs.stanford.edu>
Date: Tue, 10 Apr 2018 17:04:54 -0700
Message-ID: <87h8oimwux.fsf@ta.scs.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/cbjy0FH4dF90u1YAXKIv5janZZE>
Subject: Re: [Din] WSJ article on Identity and Blockchains
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2018 00:04:57 -0000

Thomas Hardjono <hardjono@mit.edu> writes:

> Just like there is "autonomous systems" (AS) concept in routing and
> connected via backbone routing, in the area of identity there needs to
> be the equivalent of an AS.

Yes, but obviously AS numbers are centrally allocated and a flat
namespace.  If we are going to have various identity providers, I would
argue we need two things unlike AS numbers:

  1. The identifiers should be self-authenticating (public keys, not
     integers), so allocation is "self-server," and

  2. We need some notion of a "symbolic link", so that I can name not
     just someone else's key, but someone else's name, as that's very
     powerful.

These points of course were ones that many of us were making in the
1990s.  See, for instance SPKI/SDSI.

> So anytime I hear about a global blockchain to rule them all, I cringe
> :-)

The blockchain is useful, but sort of orthogonal to the namespace
itself.  What it provides, that we couldn't do before, is the ability to
voluntarily restrict what you do with your own namespace.  E.g., maybe
you want to delegate a name and then restrict yourself from revoking it
without seven days notice.

David