Re: [openpgp] How to re-launch the OpenPGP WG

Jon Callas <jon@callas.org> Thu, 12 March 2015 18:58 UTC

Return-Path: <jon@callas.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D644A1A1B72 for <openpgp@ietfa.amsl.com>; Thu, 12 Mar 2015 11:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 7cWrO-KuYQgn for <openpgp@ietfa.amsl.com>; Thu, 12 Mar 2015 11:58:54 -0700 (PDT)
Received: from mail.merrymeet.com (merrymeet.com [173.164.244.100]) by ietfa.amsl.com (Postfix) with ESMTP id 60AB21A1BA2 for <openpgp@ietf.org>; Thu, 12 Mar 2015 11:58:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.merrymeet.com (Postfix) with ESMTP id D7A166C3CD5D; Thu, 12 Mar 2015 11:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at merrymeet.com
Received: from mail.merrymeet.com ([127.0.0.1]) by localhost (merrymeet.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1YS13KqnX62; Thu, 12 Mar 2015 11:58:11 -0700 (PDT)
Received: from keys.merrymeet.com (keys.merrymeet.com [173.164.244.97]) by mail.merrymeet.com (Postfix) with ESMTPSA id 3C3946C3CD4C; Thu, 12 Mar 2015 11:58:10 -0700 (PDT)
Received: from [10.0.23.30] ([173.164.244.98]) by keys.merrymeet.com (PGP Universal service); Thu, 12 Mar 2015 11:58:11 -0700
X-PGP-Universal: processed; by keys.merrymeet.com on Thu, 12 Mar 2015 11:58:11 -0700
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Jon Callas <jon@callas.org>
In-Reply-To: <87twxqgkmz.fsf@vigenere.g10code.de>
Date: Thu, 12 Mar 2015 11:58:09 -0700
Message-Id: <ECAAAAEA-6AEB-4F15-B12E-12676CBC87F7@callas.org>
References: <878uf2iehi.fsf@vigenere.g10code.de> <20150312133846.GA2983@singpolyma-liberty> <87twxqgkmz.fsf@vigenere.g10code.de>
To: Werner Koch <wk@gnupg.org>
X-Mailer: Apple Mail (2.2070.6)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/4auOYDQIfNNoG37q9p2cfk5oG9Y>
Cc: Stephen Paul Weber <singpolyma@singpolyma.net>, "openpgp@ietf.org OpenPGP" <openpgp@ietf.org>, Jon Callas <jon@callas.org>
Subject: Re: [openpgp] How to re-launch the OpenPGP WG
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2015 18:58:56 -0000

> On Mar 12, 2015, at 11:01 AM, Werner Koch <wk@gnupg.org> wrote:
> 
> On Thu, 12 Mar 2015 14:38, singpolyma@singpolyma.net said:
> 
>>> - A v5 key format.  Prepare for forthcoming public key algorithms.
>> 
>> What sorts of changes do you see being needed here?
> 
> In the past we collected several ideas for a v5 key format.  We need to
> revisit the list archives.  IIRC, the plan was to first wait for the
> outcome of the SHA-3 competition.

There were other things we talked about as well in V5. I think that connected and separate, a hash-independent way to do a fingerprint is called for. There was a nice proposal for that in the archives -- algorithm-id:hash-value -- the abbreviated one.

> 
>> that work is usually done under this WG as well.  Do you see moving
>> more in that direction, or a full-on new RFC coming out of proposed
>> work?
> 
> Eventually a single new RFC should be done - for a v5 format this will
> be needed anyway.

Or not -- it's a decision of the new working group.

We traditionally put everything into one document. That has a lot of advantages. There's essentially one place to check. Other WGs -- for example, S/MIME -- have a lot of separate documents. That means they can work on things in parallel, but makes it harder to wind through the mass of documents.

I think more than one but less than fifty (which is only a slight exaggeration -- the last time I checked there were over 35 S/MIME documents) is a good compromise.

But yeah, I think you'd want to revise 4880 for new stuff. There are, however, a number of ways to organize that.

	Jon