Re: [dane] I-D Action: draft-ietf-dane-openpgpkey-01.txt: keyring format definition

Petr Spacek <pspacek@redhat.com> Mon, 12 January 2015 13:52 UTC

Return-Path: <pspacek@redhat.com>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64CDB1A90F1 for <dane@ietfa.amsl.com>; Mon, 12 Jan 2015 05:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fsL3KA2qf7fY for <dane@ietfa.amsl.com>; Mon, 12 Jan 2015 05:52:26 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BDFB1A90FE for <dane@ietf.org>; Mon, 12 Jan 2015 05:52:26 -0800 (PST)
Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t0CDqPBL002803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <dane@ietf.org>; Mon, 12 Jan 2015 08:52:25 -0500
Received: from pspacek.brq.redhat.com (pspacek.brq.redhat.com [10.34.128.7]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t0CDqNUT031680 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <dane@ietf.org>; Mon, 12 Jan 2015 08:52:25 -0500
Message-ID: <54B3D197.7040808@redhat.com>
Date: Mon, 12 Jan 2015 14:52:23 +0100
From: Petr Spacek <pspacek@redhat.com>
Organization: Red Hat
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: dane@ietf.org
References: <20141027233636.24734.41333.idtracker@ietfa.amsl.com>
In-Reply-To: <20141027233636.24734.41333.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/LMpVQ9v3PK6ZsKG6Ee9Bnbrf95k>
Subject: Re: [dane] I-D Action: draft-ietf-dane-openpgpkey-01.txt: keyring format definition
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 13:52:32 -0000

On 28.10.2014 00:36, internet-drafts@ietf.org wrote:
>         Title           : Using DANE to Associate OpenPGP public keys with email addresses
>         Author          : Paul Wouters
> 	Filename        : draft-ietf-dane-openpgpkey-01.txt

I would like to see a clarification for section:

http://tools.ietf.org/html/draft-ietf-dane-openpgpkey-01#section-2.1
2.1. The OPENPGPKEY RDATA component
   The RDATA (or RHS) of an OPENPGPKEY Resource Record contains a single
   value consisting of a [RFC4880] formatted OpenPGP public keyring.


I'm struggling with definition of "formatted OpenPGP public keyring". After a
quick glance I have found only this:

http://tools.ietf.org/html/rfc4880#section-3.6
3.6. Keyrings
   A keyring is a collection of one or more keys in a file or database.
   Traditionally, a keyring is simply a sequential list of keys, but may
   be any suitable database.  It is beyond the scope of this standard to
   discuss the details of keyrings or other databases.

I did not read whole RFC 4880 so it is possible that I have missed some
related definitions but IMHO this reference deserves clarification.

Where is the actual keyring format defined?

-- 
Petr Spacek  @  Red Hat