Re: [openpgp] keyserver protocol

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Tue, 07 May 2013 15:11 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE7421F8F33 for <openpgp@ietfa.amsl.com>; Tue, 7 May 2013 08:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CTPCoxrA2Om for <openpgp@ietfa.amsl.com>; Tue, 7 May 2013 08:11:53 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by ietfa.amsl.com (Postfix) with ESMTP id 87DB921F8E2C for <openpgp@ietf.org>; Tue, 7 May 2013 08:11:53 -0700 (PDT)
Received: from fifthhorseman.net (lair.fifthhorseman.net [108.58.6.98]) by che.mayfirst.org (Postfix) with ESMTPSA id 9CFECF979; Tue, 7 May 2013 11:11:48 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 78C081FDBF; Tue, 7 May 2013 11:11:48 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Shaw <dshaw@jabberwocky.com>
In-Reply-To: <3C32E4F1-6B48-4561-94FF-7489D44E36CC@jabberwocky.com>
References: <50E5E6AE.5050201@jcea.es> <3C32E4F1-6B48-4561-94FF-7489D44E36CC@jabberwocky.com>
User-Agent: Notmuch/0.15.2 (http://notmuchmail.org) Emacs/23.4.1 (x86_64-pc-linux-gnu)
Date: Tue, 07 May 2013 11:11:45 -0400
Message-ID: <87zjw6keoe.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Cc: openpgp@ietf.org
Subject: Re: [openpgp] keyserver protocol
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 07 May 2013 15:11:58 -0000

On Thu 2013-01-03 17:53:15 -0500, David Shaw wrote:

> I actually wrote this up at one point as an informational draft, but
> for one reason or another didn't finish submitting it.  If there is
> interest, I can clean it up and submit:
>
>   http://tools.ietf.org/id/draft-shaw-openpgp-hkp-00.txt

David, i would like to see this picked back up if possible.  Is there a
way that i can help?

In particular, I would like to see the error signalling and semantics be
more clearly and explicitly defined, so that (for example) when a
keyserver has a problem the user agents (e.g. client tools like gpg
--refresh) have a clear way to distinguish between cases like:

 0) "I have no key material matching this name/keyid at all"

 1) "I have too many keys that match this search to bother you with an
     insanely long list"

 2) "something is broken in my database, and I'm confused"

and so forth.

Any thoughts on what would be reasonable next steps?

Regards

    --dkg