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

Paul Wouters <paul@nohats.ca> Tue, 14 February 2023 16:01 UTC

Return-Path: <paul@nohats.ca>
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 685A5C1CAB45 for <openpgp@ietfa.amsl.com>; Tue, 14 Feb 2023 08:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=nohats.ca
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 zcE6yb58Etts for <openpgp@ietfa.amsl.com>; Tue, 14 Feb 2023 08:01:52 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (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 23D96C1CAB3A for <openpgp@ietf.org>; Tue, 14 Feb 2023 08:01:52 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4PGQv07586zFPg; Tue, 14 Feb 2023 17:01:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1676390509; bh=eag3pBW+YJqKjQBiX0pH0GK70Homh1Qu08/M4z1os/Y=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=YWcBJ95N+mLbx9aj3YfNH3suCZLA71ol4DOkRXLoFTYgfn1g7pQph9HFfVpT5NP7Q DZ8299LMsecUJxP8IJmSSohyCHWFJp+ECEJPNW8doCRH6zzFwOMf6cUOFUeR/dQ24U kDVK4BbSOLMtI6IEIEsyGzuHDb6JdhON+i13Y/M0=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id iTbtDoKzWGvd; Tue, 14 Feb 2023 17:01:48 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 14 Feb 2023 17:01:48 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 43C007C39AC; Tue, 14 Feb 2023 11:01:47 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 4293D7C39AB; Tue, 14 Feb 2023 11:01:47 -0500 (EST)
Date: Tue, 14 Feb 2023 11:01:47 -0500
From: Paul Wouters <paul@nohats.ca>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: "openpgp@ietf.org" <openpgp@ietf.org>
In-Reply-To: <13f2e75a-0a11-8803-15a4-1ef986f9a9f9@cs.tcd.ie>
Message-ID: <c38cb3fd-0950-e1db-9627-b56a98879070@nohats.ca>
References: <SY4PR01MB6251048223366D25E14FF34FEEDE9@SY4PR01MB6251.ausprd01.prod.outlook.com> <24d23b9f-50b4-0a80-d1a5-63b20c366a54@nohats.ca> <878rh0tzkl.fsf@wheatstone.g10code.de> <072ad857-1591-cc9a-4276-d351bb2a327d@nohats.ca> <13f2e75a-0a11-8803-15a4-1ef986f9a9f9@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/XMzabO2S59tYj-UMJIFB5GAeV2w>
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: Tue, 14 Feb 2023 16:01:56 -0000

On Tue, 14 Feb 2023, Stephen Farrell wrote:

> On 14/02/2023 14:39, Paul Wouters wrote:
>>
>>  This is good point to take into consideration. Is there a way forward
>>  that takes this into account? eg for v6 we can make changes, but perhaps
>>  for v3/v4 we need to keep using the old OIDs.
>>
>>  Thanks for this input Werner.
>
> So can someone explain the benefit, other than in making
> the spec tidier in a sense, of making this change?
>
> If there're implementations that use these OIDs for some
> configuration that affects applications other than PGP
> for example, using the same/official OIDs would have a
> clear benefit, but I'm not sure if that's the case or not.

As Peter said, to reduce squating on a code point that isn't ours.
Perhaps in 10 years when v3/v4 keys are too weak/vulnerable, someone
can finally remove them from the bisbis document.

Paul