Re: [keyassure] publishing the public key

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 15 February 2011 15:30 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 A3C363A6E92 for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 07:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level:
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_40=-0.185, 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 Ea8jWQAA-7T1 for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 07:30:30 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id DD0EF3A6BA0 for <keyassure@ietf.org>; Tue, 15 Feb 2011 07:30:30 -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 p1FFUtlN099714 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Tue, 15 Feb 2011 08:30:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D5A9C2F.6050205@vpnc.org>
Date: Tue, 15 Feb 2011 07:30:55 -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: keyassure@ietf.org
References: <928BE494-C59D-4FFF-9390-C459A4BC2107@bblfish.net> <20110214124617.GA31136@LK-Perkele-VI.localdomain> <20110215022103.GA2874@odin.mars.sol> <alpine.LFD.1.10.1102142139560.3131@newtla.xelerance.com> <4D59F233.7080708@vpnc.org> <alpine.LFD.1.10.1102150009450.3131@newtla.xelerance.com>
In-Reply-To: <alpine.LFD.1.10.1102150009450.3131@newtla.xelerance.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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, 15 Feb 2011 15:30:31 -0000

On 2/14/11 9:12 PM, Paul Wouters wrote:
> On Mon, 14 Feb 2011, Paul Hoffman wrote:
>
>>> Why does TLS service have to send cert/cert chain?
>>
>> Because that is what is required by the TLS standard. We should not be
>> trying to modify the TLS spec in this WG.
>
> I understand, but there IS a relationship here. With DANE, you have an
> alternative to PKIX-TLS. So such a change would affect TLS, but would
> require DANE.

I disagree that us using bare keys for identifying TLS server 
certificates is impossible.

> Similarly, the TLS group could say "we won't add bare
> public key because there is no validation for it" and they'd send me
> back to DANE.

They could say that, but you have not even asked the TLS WG, have you?

> So please don't call bare public key out of scope yet.

Paul, saying that is ridiculous. In the message that preceded the one 
you replied to, I actually supported bare keys as long as proponents can 
propose wording that the WG would support on how they should be included.