Re: [keyassure] publishing the public key

Henry Story <henry.story@bblfish.net> Tue, 15 February 2011 11:46 UTC

Return-Path: <henry.story@bblfish.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 15D513A6CB0 for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 03:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.532
X-Spam-Level:
X-Spam-Status: No, score=-3.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 FtnKlQ2jzyHw for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 03:46:16 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id C9E6C3A6CAE for <keyassure@ietf.org>; Tue, 15 Feb 2011 03:46:15 -0800 (PST)
Received: by bwz12 with SMTP id 12so382007bwz.31 for <keyassure@ietf.org>; Tue, 15 Feb 2011 03:46:40 -0800 (PST)
Received: by 10.204.46.154 with SMTP id j26mr26022891bkf.134.1297770398910; Tue, 15 Feb 2011 03:46:38 -0800 (PST)
Received: from bblfish.home (ALagny-751-1-9-11.w83-112.abo.wanadoo.fr [83.112.80.11]) by mx.google.com with ESMTPS id x38sm2518642bkj.13.2011.02.15.03.46.36 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Feb 2011 03:46:37 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Henry Story <henry.story@bblfish.net>
In-Reply-To: <alpine.LFD.1.10.1102142033280.3131@newtla.xelerance.com>
Date: Tue, 15 Feb 2011 12:46:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B25A7EA4-8535-4695-AA9F-1DB71B89BC77@bblfish.net>
References: <E1Pp95n-0000G3-OS@login01.fos.auckland.ac.nz> <alpine.LFD.1.10.1102142033280.3131@newtla.xelerance.com>
To: Paul Wouters <paul@xelerance.com>
X-Mailer: Apple Mail (2.1082)
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 11:46:17 -0000

On 15 Feb 2011, at 02:35, 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.

Or you just put the key info in ASN.1 format (Abstract Syntax Notation 1). ASN.1 
is just like XML in this respect - both are syntaxes.  Instead of URIs for namespaces 
they use  registered numbers. And  there is part of the X509 tree of information
a subtree for describing public keys. Just take that subtree.  

I don't know where that is defined though, though I think I came across it last
year.

Henry

> 
> Paul
> _______________________________________________
> keyassure mailing list
> keyassure@ietf.org
> https://www.ietf.org/mailman/listinfo/keyassure

Social Web Architect
http://bblfish.net/