Re: [openpgp] Linked Identities / URI Attributes status

Wiktor Kwapisiewicz <wiktor@metacode.biz> Thu, 12 October 2017 13:18 UTC

Return-Path: <wiktor@metacode.biz>
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 0D9D81344E2 for <openpgp@ietfa.amsl.com>; Thu, 12 Oct 2017 06:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metacode.biz
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 EQvB3NLrn_YM for <openpgp@ietfa.amsl.com>; Thu, 12 Oct 2017 06:18:46 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 691091344E1 for <openpgp@ietf.org>; Thu, 12 Oct 2017 06:18:46 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id c82so5906424lfc.6 for <openpgp@ietf.org>; Thu, 12 Oct 2017 06:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metacode.biz; s=2011; h=subject:references:to:from:openpgp:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=3FQ/ySFQ5BDhGLRMz0DGVZfanA6Nex7T90086jBbk6M=; b=B9RnVgZ+VVlqNcG87lL/cJBP3GOFRIp+DivcV8oDLm0R5Q/89HnvDSuSJl++4DGUbJ lX3nrfOxlfJNqEHaImCzWYUediEpVLfKVwNHtV3o0WXzA10dcHe9E8kgQCBcFIS1ydTS Fq1hGsazFj8it7eVSxpH2uDw3HO+Ag0TM30/A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:openpgp:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding:content-language; bh=3FQ/ySFQ5BDhGLRMz0DGVZfanA6Nex7T90086jBbk6M=; b=f2xkw680CLIkPhGw36GW22sScHUKiy6y47gyyzyDS65aP+MXxJp5P8fG+7qEmbysX5 SNqBeWReo143ZqwvHFPbtIVUKlV17ihE0YW/u5CKqBlt515NQ3YZYWKaPqcgWcWOk+sF BBWhuetyc7TpAbQ7CNDQXULCnpozPWmIamEAY9+kVvxL5S7TdjHwEMcxmmX5ZguIv7IP YNwKy/ypCG3DEi+zMlADTxcLAqfDgjzITWDSe+WJa0G7/mpD+h4GBa8GWqL+Y6WQki5A XHYFAITPooRXZsgMyFOnj4qdQ62VhXjB4khlDWNSO99bgkjsD74/M9Zp9o78VMnYuJ6F JCSg==
X-Gm-Message-State: AMCzsaWe45tvhZgq2JOM2HmlLsHiuHwKBh+s/m/n7QdHnHf9/gWeNTk1 epKE+zCszYDq5ZO+O/oiRqLmCTM/Xuo=
X-Google-Smtp-Source: ABhQp+QxnVcfv+jQfR2YtIBeJZveEIrBH+p52GFesAtyjD4XbooNiNittsmD4FGBkpwDRdrQs3mdlQ==
X-Received: by 10.46.34.129 with SMTP id i123mr123680lji.106.1507814324438; Thu, 12 Oct 2017 06:18:44 -0700 (PDT)
Received: from [192.168.1.69] (89-64-37-77.dynamic.chello.pl. [89.64.37.77]) by smtp.googlemail.com with ESMTPSA id q67sm3632153lja.19.2017.10.12.06.18.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Oct 2017 06:18:43 -0700 (PDT)
References: <43412d30-51a2-1941-43d9-f0207f77afcd@metacode.biz> <874lrctv76.fsf@wheatstone.g10code.de>
To: Werner Koch <wk@gnupg.org>, openpgp@ietf.org
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
Openpgp: id=653909A2F0E37C106F5FAF546C8857E0D8E8F074
Organization: Metacode
Message-ID: <8dc32ddd-307a-d0a9-2bda-0497cec4cba0@metacode.biz>
Date: Thu, 12 Oct 2017 15:18:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <874lrctv76.fsf@wheatstone.g10code.de>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/FgN16dwb5E8HahHbqK1I_sQsOEg>
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: Thu, 12 Oct 2017 13:18:49 -0000

> 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.

This is an excellent idea. Coupled with signature notation data, that
can be made critical one can assure that unknown Linked Identity UIDs
would be considered invalid by software that does not understand a
particular notation data proof.

Not to mention UIDs and Notation Data can be added using command line
tools that already exist.

But I do have to agree with Vincent that if UATs are deprecated they
should be marked as such.

Actually, previously I got a very different impression when I diffed RFC
4880 and 4880 bis-02 and saw new section "5.13.2.  User ID Attribute
Subpacket" [0] that was introduced for Device Certificates [1]. Is this
something old to be removed or an entirely different case?

Kind regards,

Wiktor

[0]:
https://tools.ietf.org/html/draft-ietf-openpgp-rfc4880bis-02#section-5.13.2

[1]: https://www.ietf.org/mail-archive/web/openpgp/current/msg08460.html