potential IETF WG incompatibility with GnuPG 2.3

[Andrew Gallagher]

On 19 Dec 2022, at 09:19, Bernhard Reiter <bernhard at intevation.de> wrote:
> 
> Signed PGP part
> Hey Vincent,
> 
> Am Donnerstag 15 Dezember 2022 15:05:38 schrieb Vincent Breitmoser via
> Gnupg-devel:
>> The quoted commit is a big decision for GnuPG.
> 
> and the WG decision to become incompatible with the previous drafts
> were a big decision for the working group affecting
> OpenPGP users, implementations and the wider ecosystem.
> 
> What are their plans for this problem?

To be fair to Vincent, he doesn’t answer for the WG (and neither do I). The chairs have recommended that all reasonable effort be made to remove breaking incompatibilities between -bis and crypto-refresh:

https://mailarchive.ietf.org/arch/msg/openpgp/yayGaIen3DW6ixwrJkP-QcAcFSQ/

However this has not prevented a lot of unhelpful and premature speculation about forking the standard or skipping version numbers to avoid dealing with the issue.

A

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20221219/8affff69/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: favicon.ico
Type: image/vnd.microsoft.icon
Size: 3638 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20221219/8affff69/attachment.ico>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20221219/8affff69/attachment.sig>