Re: I-D ACTION:draft-ietf-openpgp-rfc2440bis-06.txt

Jon Callas <jon@callas.org> Tue, 13 August 2002 06:25 UTC

Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02505 for <openpgp-archive@lists.ietf.org>; Tue, 13 Aug 2002 02:25:52 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7D6EhP20963 for ietf-openpgp-bks; Mon, 12 Aug 2002 23:14:43 -0700 (PDT)
Received: from merrymeet.com (merrymeet.com [63.73.97.162]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7D6Egw20955 for <ietf-openpgp@imc.org>; Mon, 12 Aug 2002 23:14:42 -0700 (PDT)
Received: from [63.73.97.182] (63.73.97.182) by merrymeet.com with ESMTP (Eudora Internet Mail Server 3.1.2); Mon, 12 Aug 2002 23:14:45 -0700
User-Agent: Microsoft-Entourage/10.1.0.2006
Date: Mon, 12 Aug 2002 23:14:49 -0700
Subject: Re: I-D ACTION:draft-ietf-openpgp-rfc2440bis-06.txt
From: Jon Callas <jon@callas.org>
To: Len Sassaman <rabbi@quickie.net>, OpenPGP <ietf-openpgp@imc.org>
Message-ID: <B97DF1E9.704E%jon@callas.org>
In-Reply-To: <Pine.LNX.4.30.QNWS.0208121051070.25997-100000@thetis.deor.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>
Content-Transfer-Encoding: 7bit

> I think that it would be nice to have the NAI X.509 packets documented.
> Having quasi-offical data formats that implimentors need to deal with, but
> are not documented, sounds like a bad idea to me. (Though, if it belongs
> in a seperate Internet Draft, I have no problem with that. But there
> should be some place to go other than the PGP source for this
> information.)

It would be nice, but we have to get the owners of that code base to be
willing to document it, or have someone else do it. I presume there's
consensus that this is a good idea, as there are no further comments?

I want to get soon a new RFC number, so let's look at what there is to
finish up.

* I've completely spaced on the notary signatures, apparently, so I'll get
those in soon. 

* I'll look at signature subpackets, and if the spec needs changes to jibe
with reality, I'll do it. MUSTs changed to SHOULDs, right?

Anything else?

    Jon