IETF Logo Mail Archive

Re: [keyassure] publishing the public key

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 22 February 2011 15:43 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 316203A692C for <keyassure@core3.amsl.com>; Tue, 22 Feb 2011 07:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.38
X-Spam-Level:
X-Spam-Status: No, score=-101.38 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 j41iWhV3y07z for <keyassure@core3.amsl.com>; Tue, 22 Feb 2011 07:43:35 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 5A8E83A693A for <keyassure@ietf.org>; Tue, 22 Feb 2011 07:43:35 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1MFcDLm046866 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 22 Feb 2011 08:38:14 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D63D865.70704@vpnc.org>
Date: Tue, 22 Feb 2011 07:38:13 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Henry Story <henry.story@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> <p06240803c98892e88fc4@[59.188.192.152]> <1FAB667F-44F9-4349-B11B-F4FECD51BB81@bblfish.net> <p06240804c988c84933b6@[169.223.137.111]> <B6315D18-AE32-4CE8-A7A5-7D155C1F259B@bblfish.net>
In-Reply-To: <B6315D18-AE32-4CE8-A7A5-7D155C1F259B@bblfish.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Tue, 22 Feb 2011 15:43:36 -0000

Henry: It feels like you are pushing for DANE and WebID to have "bare 
public key" as a way of doing certificate identification without 
justification for how this could be useful in DANE. Without taking any 
stance on WebID, I find this frustrating as the document co-author in 
DANE. The two protocols do not have the same targets and do not even run 
over the same transports.

Could you please re-split the discussion and, in the DANE part, be much 
more specific about how you see bare public keys in DANE being used with 
just TLS? Thanks!

v2.23.0 | Report a Bug | By Email