Re: [openpgp] lack of agenda items...

Vincent Breitmoser <look@my.amazin.horse> Wed, 02 November 2022 17:25 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 4B23BC1522CF for <openpgp@ietfa.amsl.com>; Wed, 2 Nov 2022 10:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 XYdtXOVeyJIy for <openpgp@ietfa.amsl.com>; Wed, 2 Nov 2022 10:25:43 -0700 (PDT)
Received: from my.amazin.horse (my.amazin.horse [5.181.49.53]) (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 E5CB7C14CE3D for <openpgp@ietf.org>; Wed, 2 Nov 2022 10:25:42 -0700 (PDT)
Received: from [172.27.30.181] (business-90-187-201-249.pool2.vodafone-ip.de [90.187.201.249]) (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 5EEA66181D for <openpgp@ietf.org>; Wed, 2 Nov 2022 18:25:40 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=my.amazin.horse; s=2020; t=1667409940; bh=1mSpna1iuVFyM2MroXLgboL/75XSbqmQ9CzNpv6pjOM=; h=Date:To:References:From:Subject:In-Reply-To; b=j/vzJN+p45yi9IsGeN8Kp6AYeLnPHP9dqK7jSJjXA3DHa/kbhpEa0qClloZOUaltU H7dueeaiPOa9EmUZG3BiMi/WmiheWu35W0Xlo5xLp1Iorh8UwJ6dJA5CbnIRM9twnV jKJe2JFVd1uGuo3ZAVjUwPVFwg9D7eFeKyo+iQlI=
Message-ID: <70128752-1a8f-194b-e238-a829e75361d2@my.amazin.horse>
Date: Wed, 02 Nov 2022 18:25:39 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0
Content-Language: en-US
To: openpgp@ietf.org
References: <c859b8da-5fd6-297b-f30b-39805e3e3cad@cs.tcd.ie> <49O_0HJ65X78GDB09nBKcdWl3GxD5gVeCrWSNSEB4Jq08w3GRVUe1eUEr4wOmilsDf5F0eQaSc0fhgGhYTitOC6ofO6_yz7HiScPXBiZdtQ=@protonmail.com>
From: Vincent Breitmoser <look@my.amazin.horse>
In-Reply-To: <49O_0HJ65X78GDB09nBKcdWl3GxD5gVeCrWSNSEB4Jq08w3GRVUe1eUEr4wOmilsDf5F0eQaSc0fhgGhYTitOC6ofO6_yz7HiScPXBiZdtQ=@protonmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/kNvKFTgQ7tAA34-Y5ARhedphJiM>
Subject: Re: [openpgp] lack of agenda items...
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, 02 Nov 2022 17:25:47 -0000

Hey list,

On 02.11.22 18:11, Daniel Huigens wrote:
>> *where feasible*, reduce potential conflicts with Werner's draft
> I know that that message asks for specific text, and I'd be willing to
> propose some, but I'm not entirely sure what direction to go in.
>
> For example, do we want to bump keys and signatures to v6? That would be
> a crude but simple way to ensure interoperability. More fine-grained
> changes to ensure that crypto-refresh-v5 keys and signatures inter-
> operate with draft-koch-v5 keys and signatures would take a lot more
> work, which I'd prefer to only do if the WG decides that that's the
> best way to go.

In a related bit of news, GnuPG has as of 2022-10-31 removed its 
"--rfc4880bis"
compatibility mode, and adopted it (i.e. draft-koch-v5) as default behavior.

https://dev.gnupg.org/rG4583f4fe2e11b3dd070066628c3f16776cc74f72

Take this with a grain of salt: I'm not 100% sure I read the commit 
right (if that's
the case please someone correct me!), and of course the underlying 
intent isn't
fully clear from a possibly intermediate commit. I asked for 
clarification directly
on the commit, to be sure.

Cheers

  - V