Standards: IETF WG proposing incompatible despite implementations and objections

[Bernhard Reiter]

Hi,

what happened the overhauled specifications of OpenPGP?

It seems that the IETF working group 
plans to publish their proposal of an updated OpenPGP specification
a) even with objections present
b) and three major implementations 
 RNP (used by Thunderbird)
 GnuPG and
 OpenPGP.js (used by Mailvelope)
present that have deployed and are using a set of new functions
that GnuPG has documented and considered a rough consensus until 2021.

Some technical arguments on this mailing lists have been brought up
in the last months, but I am not sure if they have been considered by the 
working group. The email discussion archived end of march at
  https://mailarchive.ietf.org/arch/msg/openpgp/pNkkw2r16G-q_O0Nd6eL-JFLMXU/
just shows procedural arguments refering to a resolution in September.

A good paths forward would be, if the technical arguments would be 
re-considered, and deployed implementations.

Regards
Bernhard
-- 
https://intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20230426/fda8281a/attachment.sig>