Re: [openpgp] Linked Identities / URI Attributes status

Werner Koch <wk@gnupg.org> Fri, 06 October 2017 10:48 UTC

Return-Path: <wk@gnupg.org>
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 D29B0134905 for <openpgp@ietfa.amsl.com>; Fri, 6 Oct 2017 03:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=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 iJdP8AY54v2g for <openpgp@ietfa.amsl.com>; Fri, 6 Oct 2017 03:48:38 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (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 8DE66134904 for <openpgp@ietf.org>; Fri, 6 Oct 2017 03:48:38 -0700 (PDT)
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1e0QBI-0001ub-PK for <openpgp@ietf.org>; Fri, 06 Oct 2017 12:48:36 +0200
Received: from wk by wheatstone.g10code.de with local (Exim 4.84 #3 (Debian)) id 1e0Q4J-0002XF-If; Fri, 06 Oct 2017 12:41:23 +0200
From: Werner Koch <wk@gnupg.org>
To: Wiktor Kwapisiewicz <wiktor@metacode.biz>
Cc: openpgp@ietf.org
References: <43412d30-51a2-1941-43d9-f0207f77afcd@metacode.biz>
Organisation: The GnuPG Project
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Mail-Followup-To: Wiktor Kwapisiewicz <wiktor@metacode.biz>, openpgp@ietf.org
Date: Fri, 06 Oct 2017 12:41:17 +0200
In-Reply-To: <43412d30-51a2-1941-43d9-f0207f77afcd@metacode.biz> (Wiktor Kwapisiewicz's message of "Fri, 6 Oct 2017 11:11:34 +0200")
Message-ID: <874lrctv76.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=bluebird_Albanian_freedom_Semtex_War_on_Terrorism_Glock_BCCI_anthrax"; micalg=pgp-sha256; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/36zgFe7WKnheRySJSJin3pcB3y0>
Subject: Re: [openpgp] Linked Identities / URI Attributes status
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 06 Oct 2017 10:48:40 -0000

On Fri,  6 Oct 2017 11:11, wiktor@metacode.biz said:

> Is there anything that blocks URI Attributes [1] from being approved and
> having an official (2-99) User Attribute type?

I was not aware of that (expired) I-D.  Anyway, I think that the User
Attributes should not be extended over their use for an image.  URIs can
simply be represented by plain User IDs and software can easily detected
such URIs if desired.

The need to implement UAT only adds more complexity for a questionable
purpose.  Note that these image UAT were introduced due to marketing
needs of PGP or NAT and (iirc) only specified after they had been
introduced in their software.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.