Re: [keyassure] Issue #14 - publishing the public key

Warren Kumari <warren@kumari.net> Tue, 15 February 2011 02:25 UTC

Return-Path: <warren@kumari.net>
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 1678C3A6E19 for <keyassure@core3.amsl.com>; Mon, 14 Feb 2011 18:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 dIpPvCVwO1Bu for <keyassure@core3.amsl.com>; Mon, 14 Feb 2011 18:25:53 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id 0AA093A6C39 for <keyassure@ietf.org>; Mon, 14 Feb 2011 18:25:52 -0800 (PST)
Received: from [172.26.49.198] (unknown [72.14.228.1]) by vimes.kumari.net (Postfix) with ESMTPSA id 7D3C01B40921; Mon, 14 Feb 2011 21:26:16 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <alpine.LFD.1.10.1102142033280.3131@newtla.xelerance.com>
Date: Mon, 14 Feb 2011 21:26:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <276E4E98-EAB9-4C11-9FD1-08B6B7F73FFE@kumari.net>
References: <E1Pp95n-0000G3-OS@login01.fos.auckland.ac.nz> <alpine.LFD.1.10.1102142033280.3131@newtla.xelerance.com>
To: keyassure@ietf.org
X-Mailer: Apple Mail (2.1081)
Subject: Re: [keyassure] Issue #14 - 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:25:54 -0000

[ Subject updated to include the issue number - apologies if this makes your MUA crazy. ] 

We have this particular item listed as an issue in the issue tracker so I figured that we might as well keep track of the progress we are making on this, so let's discuss it an issue and figure out how / what we would like to do about it[0]... (Also known as, issue #14 is officially open :-))

W

[0]: Yes, I realize that we are already discussing it, but I'm trying hard to use the issue tracker to actually work through the open issues, track what we are deciding, etc. I have seen it being used very effectively, especially to help newcomers understand what has been discussed and what has been decided.



On Feb 14, 2011, at 8:35 PM, Paul Wouters wrote:

> 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
> _______________________________________________
> keyassure mailing list
> keyassure@ietf.org
> https://www.ietf.org/mailman/listinfo/keyassure
>