Re: [openpgp] Revoking Keys: Adding a superceded-by parameter

"Neal H. Walfield" <neal@walfield.org> Sun, 26 July 2015 02:16 UTC

Return-Path: <neal@walfield.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 C5B6D1ACEF4 for <openpgp@ietfa.amsl.com>; Sat, 25 Jul 2015 19:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.151
X-Spam-Level:
X-Spam-Status: No, score=-0.151 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
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 H-2UQns9ulNy for <openpgp@ietfa.amsl.com>; Sat, 25 Jul 2015 19:16:32 -0700 (PDT)
Received: from mail.dasr.de (mail.dasr.de [217.69.77.164]) by ietfa.amsl.com (Postfix) with ESMTP id 90D2F1ACEF2 for <openpgp@ietf.org>; Sat, 25 Jul 2015 19:16:32 -0700 (PDT)
Received: from p50813e87.dip0.t-ipconnect.de ([80.129.62.135] helo=mail.huenfield.org) by mail.dasr.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from <neal@walfield.org>) id 1ZJBUJ-0000gf-8f; Sun, 26 Jul 2015 02:16:27 +0000
Received: from grit.huenfield.org ([192.168.20.253]) by mail.huenfield.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <neal@walfield.org>) id 1ZJBUH-0001Do-Gm; Sun, 26 Jul 2015 04:16:26 +0200
Received: from ip6-localhost.huenfield.org ([::1] helo=grit.huenfield.org.walfield.org) by grit.huenfield.org with esmtp (Exim 4.84) (envelope-from <neal@walfield.org>) id 1ZJBUG-0000LY-G1; Sun, 26 Jul 2015 04:16:24 +0200
Date: Sun, 26 Jul 2015 04:16:24 +0200
Message-ID: <87a8ujoe87.wl-neal@walfield.org>
From: "Neal H. Walfield" <neal@walfield.org>
To: Vincent Breitmoser <look@my.amazin.horse>
In-Reply-To: <874mks7yx1.fsf@littlepip.fritz.box>
References: <87wpxvjf9d.wl-neal@walfield.org> <87d1zmlv3p.fsf@vigenere.g10code.de> <87twsyk35z.wl-neal@walfield.org> <87y4i9je9f.fsf@alice.fifthhorseman.net> <87h9osnswg.wl-neal@walfield.org> <874mks7yx1.fsf@littlepip.fritz.box>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.4 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-SA-Exim-Connect-IP: 192.168.20.253
X-SA-Exim-Mail-From: neal@walfield.org
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 17:06:47 +0000)
X-SA-Exim-Scanned: Yes (on mail.huenfield.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/AOFvC1X5PFFPz84cDxfwcyUKQqM>
Cc: IETF OpenPGP <openpgp@ietf.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: [openpgp] Revoking Keys: Adding a superceded-by parameter
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 26 Jul 2015 02:16:33 -0000

Hi,

At Sat, 25 Jul 2015 22:41:30 +0200,
Vincent Breitmoser wrote:
> On 25 Jul 2015, Neal H. Walfield wrote:
> > I decided to use a notation rather than a new signature subpacket.
> > This is because the signature subpacket namespace is tiny compared
> > to the notation data's namespace.
> 
> I think I disagree with this.  It's true that the signature subpacket
> namespace is not very large, but the numbers are that only ~30 subpacket
> ids out of 100 are actually used.  If we ever get past 70, we might want
> to think about how to deal with the problem (there is always the 8th bit
> left for this purpose, too), until then unused namespace is wasted
> namespace and we gain nothing by avoiding its use.
> 
> Are there any other standardized uses for the notation namespace? I am
> only aware of proposed ones, and none which have very widespread use
> outside of closed systems.

Are you arguing that since notations aren't used in practice that they
are probably not widely supported and it would be better to use a new
signature subpacket?  If not, what is your argument against
introducing a notation?

Thanks!

:) Neal