Re: [openpgp] Weird OIDs in the 4880bis draft

Vincent Breitmoser <look@my.amazin.horse> Wed, 22 February 2023 16:56 UTC

Return-Path: <look@my.amazin.horse>
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 290FCC1524DC for <openpgp@ietfa.amsl.com>; Wed, 22 Feb 2023 08:56:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=my.amazin.horse
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfBKp_gcOdcH for <openpgp@ietfa.amsl.com>; Wed, 22 Feb 2023 08:56:45 -0800 (PST)
Received: from my.amazin.horse (my.amazin.horse [IPv6:2a03:4000:3f:29c::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C52D5C1782C9 for <openpgp@ietf.org>; Wed, 22 Feb 2023 08:56:45 -0800 (PST)
Received: from [192.168.188.22] (ip4d149e63.dynamic.kabel-deutschland.de [77.20.158.99]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by my.amazin.horse (Postfix) with ESMTPSA id 65F5B61EB5 for <openpgp@ietf.org>; Wed, 22 Feb 2023 17:56:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=my.amazin.horse; s=2020; t=1677085003; bh=TbDq/p6ow0Y2zw/EJWZDIZTsVYThJX9ta8H5/UKrERY=; h=Date:To:References:From:Subject:In-Reply-To; b=td9+gz8Q1qbcyT269KdY/TUBH0gPa//mVaseH/OtYMrzb7MYWGWLg4cqV1Z6tgG7Z elhqa4tqha0yUkPQdx4Mjmd/e6Vk7bBbKz+7NnrVg8rHuE27zFH0gj5l5vglVy2pbh PeAPDFVKAi1SIr9Gc+yiL6gFrLPal0r7pUgwGjCI=
Message-ID: <850d0abb-03cd-0815-b3d3-6db2fe9d72da@my.amazin.horse>
Date: Wed, 22 Feb 2023 17:56:42 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
To: openpgp@ietf.org
References: <SY4PR01MB6251BD1B19BAD5DE910A1C0EEED99@SY4PR01MB6251.ausprd01.prod.outlook.com> <5bbca9f6-9fc5-3e8b-51eb-103637a6a4b5@cs.tcd.ie> <877cwg9n2y.fsf@europ.lan> <87sff4jfrp.fsf@fifthhorseman.net> <874jrk9eq9.fsf@europ.lan> <4123011c-ba72-e36f-c3c9-b1da3ed33d85@cs.tcd.ie> <uyfPffB5ZDa2AJavNntu4iKXNnG4m0TlhoaDcT5fAW9lh_QkhKaJiKNAL9kelDovGhUC_xcnTsdfQjPskuXL2Byy323mlgVsR8d8AWxXVz8=@protonmail.com> <cddeb76e-59f7-5abb-e980-5b7bd8c3a419@cs.tcd.ie> <9smwivJ9SgD6TyUrzBwAWZRror46JwRIG5AqFvvCssKV98Gxu3C0H731XgfRyTZwwh4tG0ZDehjXTXX7CpqK4Z9468j_C2mi0TM1QdJRXVA=@protonmail.com> <d0a872ba-d917-0c04-845b-5862a251b444@cs.tcd.ie>
Content-Language: en-US
From: Vincent Breitmoser <look@my.amazin.horse>
In-Reply-To: <d0a872ba-d917-0c04-845b-5862a251b444@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/HdQ90vM0r8OLks0qNdajuA2K8Pw>
Subject: Re: [openpgp] Weird OIDs in the 4880bis draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 22 Feb 2023 16:56:51 -0000

Hey list,

> Ok, so given the proponents are now happy with this merge
> request can other people please take a look and express an
> opinion on the list as to whether we should make these
> changes now.
>
> Please do so by the end of Wednesday if you can.
>
> Silence on the list I guess has to mean not making these
> changes.
>
I've read the MR [!242], and I also think it should be included. I 
recall while implementing 25519
in OpenKeychain, the handling of 25519 as part of ECDH stood out as 
particularly ugly and
unidiomatic code. This change should improve that a lot.

Independently of implementation issues, I also believe this sets a 
better precedent on how
algorithm ids should be used in the future in OpenPGP. It's important to 
improve approachability
in this regard, and better incentivize implementations to actually 
coordinate and standardize their
stuff, rather than working around the spec by overloading mechanisms in 
unintended ways.

  - V