Re: [keyassure] publishing the public key

Paul Wouters <paul@xelerance.com> Tue, 15 February 2011 02:49 UTC

Return-Path: <paul@xelerance.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 5545E3A6C2B for <keyassure@core3.amsl.com>; Mon, 14 Feb 2011 18:49:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 r3OAWtAtwRaA for <keyassure@core3.amsl.com>; Mon, 14 Feb 2011 18:49:24 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id 4771D3A6C27 for <keyassure@ietf.org>; Mon, 14 Feb 2011 18:49:24 -0800 (PST)
Received: from tla.xelerance.com (tla.xelerance.com [193.110.157.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id 3009DC57C; Mon, 14 Feb 2011 21:49:48 -0500 (EST)
Date: Mon, 14 Feb 2011 21:49:47 -0500
From: Paul Wouters <paul@xelerance.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
In-Reply-To: <E1PpApf-00066M-H2@login01.fos.auckland.ac.nz>
Message-ID: <alpine.LFD.1.10.1102142148260.3131@newtla.xelerance.com>
References: <E1PpApf-00066M-H2@login01.fos.auckland.ac.nz>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: keyassure@ietf.org, paul.hoffman@vpnc.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, 15 Feb 2011 02:49:25 -0000

On Tue, 15 Feb 2011, Peter Gutmann wrote:

> A public key contains a number of components and options. For example for ECC
> there are the basic key values p, a, b, G, n, h (or m, f, a, b, G, n, h for
> binary curves), an indication of the underlying field (prime or binary), the
> point format, whether point compression is used, polynomial vs. normal basis,
> whether fixed domain parameters are used, and probably some other stuff I've
> forgotten.  How is all this stuff communicated?

I see.

> this (a) ain't gonna cut it because it doesn't cover what's required by TLS
> and (b) requires that your TLS implementation speak DNSSEC (or at least the
> DNSKEY part of DNSSEC) just to get a key. I can't see TLS implementors being
> too enthusiastic about this.

Okay.

I'll have to do some more reading to ensure I understand everything, and I'll
write up something for this for you to check.

Thanks!

Paul