Re: [keyassure] publishing the public key

Stephen Kent <kent@bbn.com> Mon, 21 February 2011 22:21 UTC

Return-Path: <kent@bbn.com>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0AF33A717A for <keyassure@core3.amsl.com>; Mon, 21 Feb 2011 14:21:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level:
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOG4UAnfC3rq for <keyassure@core3.amsl.com>; Mon, 21 Feb 2011 14:21:32 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 4DC5B3A716D for <keyassure@ietf.org>; Mon, 21 Feb 2011 14:21:32 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15]:38956 helo=[59.188.192.152]) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Pre8u-000LNm-13; Mon, 21 Feb 2011 17:22:08 -0500
Mime-Version: 1.0
Message-Id: <p06240803c98892e88fc4@[59.188.192.152]>
In-Reply-To: <93E9FABD-A84A-4A4E-AF96-6E101604F8B4@bblfish.net>
References: <E1PqbpT-0000pd-Kz@login01.fos.auckland.ac.nz> <alpine.LFD.1.10.1102201747370.26752@newtla.xelerance.com> <4D619C94.8090702@vpnc.org> <93E9FABD-A84A-4A4E-AF96-6E101604F8B4@bblfish.net>
Date: Mon, 21 Feb 2011 17:10:53 -0500
To: Henry Story <henry.story@bblfish.net>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: WebID Incubator Group WG <public-xg-webid@w3.org>, keyassure@ietf.org
Subject: Re: [keyassure] publishing the public key
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2011 22:21:33 -0000

At 4:29 PM +0100 2/21/11, Henry Story wrote:
>(Just a summary of what I understood of this thread, and a few new ideas)
>
>On 20 Feb 2011, at 23:58, Paul Hoffman wrote:
>
>>  On 2/20/11 2:51 PM, Paul Wouters wrote:
>>>  The whole point is we do not want to identify a cert. We want to 
>>>identify a key.
>>
>>  That's not the case currently, at least for many of us. Given that 
>>the only thing that can be used in TLS to identify the server is a 
>>certificate, most of us want to identify that certificate (or a 
>>trust anchor that the certificate chains to).
>
>One needs to go beyond appearances a little here. My argument is 
>that what identifies a server in TLS is a public key.

Do you mean "identifies" or "authenticates?" I think most folks view 
the DNS name (or URL) as the identity of the web site. We're debating 
the mechanics
of how to enable a client to verify that the asserted identity 
matches the client's expectations, based on the content of a series 
of DNS records.

Steve