IETF Logo Mail Archive

Re: [keyassure] publishing the public key

Paul Wouters <paul@xelerance.com> Tue, 15 February 2011 01:34 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 4C51D3A6DF7 for <keyassure@core3.amsl.com>; Mon, 14 Feb 2011 17:34:56 -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=[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 fR3LM9UUzeVL for <keyassure@core3.amsl.com>; Mon, 14 Feb 2011 17:34:55 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id E9C633A6A0C for <keyassure@ietf.org>; Mon, 14 Feb 2011 17:34:54 -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 72D00C504; Mon, 14 Feb 2011 20:35:17 -0500 (EST)
Date: Mon, 14 Feb 2011 20:35:16 -0500
From: Paul Wouters <paul@xelerance.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
In-Reply-To: <E1Pp95n-0000G3-OS@login01.fos.auckland.ac.nz>
Message-ID: <alpine.LFD.1.10.1102142033280.3131@newtla.xelerance.com>
References: <E1Pp95n-0000G3-OS@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
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 01:34:56 -0000

On Tue, 15 Feb 2011, Peter Gutmann wrote:

>> The public key's type and raw blob will be obtained from DNSSEC, so this is
>> no longer required to be conveyed to the client from the server via a PKIX
>> certificate or other ASN.1 structures.
>
> But what format is the "type and raw blob" in?  You need some way of encoding
> it, and if it's not the standard ASN.1 format what are you going to use?

I'm not sure I understand your question. The key would encoded in DNS, likely in a
format similar to DNSKEY.

Paul

v2.23.0 | Report a Bug | By Email