Re: [openpgp] Overhauling User IDs / Standardizing User Attributes

Leo Gaspard <ietf@leo.gaspard.ninja> Sat, 30 June 2018 12:43 UTC

Return-Path: <ietf@leo.gaspard.ninja>
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 67DDC1310B9 for <openpgp@ietfa.amsl.com>; Sat, 30 Jun 2018 05:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=leo.gaspard.ninja
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 SsyOlByEgSq2 for <openpgp@ietfa.amsl.com>; Sat, 30 Jun 2018 05:43:49 -0700 (PDT)
Received: from smtp.gaspard.ninja (grym.ekleog.org [94.23.42.210]) (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 F332F130DFA for <openpgp@ietf.org>; Sat, 30 Jun 2018 05:43:48 -0700 (PDT)
Received: by smtp.gaspard.ninja (OpenSMTPD) with ESMTP id abd838c8 for <openpgp@ietf.org>; Sat, 30 Jun 2018 12:43:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=leo.gaspard.ninja; h=subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s= grym-20170528; bh=Z+AjEScd2BzjfFizCKBWqZoCcwA=; b=sVFdiF9qmvtbjR EpxSKQNkZ84VrayJ/DQkQEsv26z66BFPxi/79vW7mHvUE+ah8UeUIYdAaAklsD2X cGg/JyAOx4YKCsLEOiX/KMOCFO6xr+1hPDuTfcOIMvFCFcuzW+lXVk0lR3XlNE8i WBXXNU91ROydDYI/PN5bcicayNNe4=
Received: by smtp.gaspard.ninja (OpenSMTPD) with ESMTPSA id 3568deb1 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for <openpgp@ietf.org>; Sat, 30 Jun 2018 12:43:44 +0000 (UTC)
To: openpgp@ietf.org
References: <39e598e1-2bc0-32c9-3489-4bb6ca2a631b@leo.gaspard.ninja> <871sdw24yd.wl-neal@walfield.org> <c2e6bbe7-0694-8193-bb76-dd50fde7d967@leo.gaspard.ninja> <d28d8f8b-b261-eb29-97bc-9c7159a62ce6@leo.gaspard.ninja> <118e5b9d-de9e-aa14-d8b4-19ef259f3d0a@ruhr-uni-bochum.de> <e63924fe-95b2-dcf8-5726-b0497945ac74@leo.gaspard.ninja> <f31349e2-e509-4e06-6db5-2ff0ffb213a5@ruhr-uni-bochum.de> <3996841a-b6ae-8769-2de8-b35351c54719@leo.gaspard.ninja> <8E4410C7-9370-492C-838F-857983CA67FC@icloud.com> <8a608b9f-f96b-466d-a0b8-7d1aa39ab011@leo.gaspard.ninja> <D3567617-4B9B-4BFE-AC39-11B0BEBB0B6B@icloud.com> <1cacc056-1ec7-f388-ee08-46468bd87bda@metacode.biz> <bae4a6ec-36b5-6837-0b88-d009de139111@leo.gaspard.ninja> <sjmwouhv84f.fsf@securerf.ihtfp.org>
From: Leo Gaspard <ietf@leo.gaspard.ninja>
Message-ID: <a9c56806-a652-921e-d605-cd17ef982001@leo.gaspard.ninja>
Date: Sat, 30 Jun 2018 21:43:40 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <sjmwouhv84f.fsf@securerf.ihtfp.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/RMyqn0GOIlJX1LD2d7b0HUhnRPs>
Subject: Re: [openpgp] Overhauling User IDs / Standardizing User Attributes
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.26
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: Sat, 30 Jun 2018 12:43:52 -0000

On 06/30/2018 02:02 AM, Derek Atkins wrote:
> Leo Gaspard <ietf=40leo.gaspard.ninja@dmarc.ietf.org> writes:
> 
>> Well, User IDs are not easier to work with than User Attributes. The
>> only difference is that User IDs have been defined to be free-form
>> UTF-8, while the only User Attribute that has been defined (up to now)
>> is the picture type. And thus the only User Attribute that's easy to
>> work with is the picture User Attribute… which sounds logical.
>>
>> OTOH, supposing my idea was introduced, then the additionally-defined
>> User Attributes would become mandatorily supported in v5 keys (among
>> other reasons because there would no longer be any User ID), and there
>> would be a free-form tag=value type (with both tag and value being UTF-8).
> 
> May I point you to the (expired) document,
> draft-atkins-openpgp-device-certificates which started down the road of
> adding additional Attribute packets.
> 
> Would something like that help?

Indeed, I hadn't seen this!

This is adding a User Attribute subpacket type for a reason completely
different from the reason I have, and even going a bit in opposition to
the movement I was trying to set (which would have led to the definition
of a “Device ID” attribute subpacket type that wouldn't “by convention,
[include] a mail name-addr”, because that possibly makes no sense, and
if it does it can be replicated with “Device ID” + “email” attribute
subpackets).

But the idea of adding User Attributes that are actually readable by
humans is the same, so that they can be easily understood by humans even
when using implementations that can't fully handle them (only the bare
minimum of displaying UTF-8) :)