From gnupg-devel Fri Apr 28 08:03:44 2023 From: Bernhard Reiter Date: Fri, 28 Apr 2023 08:03:44 +0000 To: gnupg-devel Subject: draft fundamental points (pointer) (Re: Standards: IETF WG proposing incompatible despite implementa Message-Id: <202304281003.44996.bernhard () intevation ! de> X-MARC-Message: https://marc.info/?l=gnupg-devel&m=168266906018699 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============8417150722298022737==" --===============8417150722298022737== Content-Type: multipart/signed; boundary="nextPart3495381.Oz5GEdysoT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart3495381.Oz5GEdysoT Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag 27 April 2023 19:04:02 schrieb Andrew Gallagher via Gnupg-dev= el: > On 27 Apr 2023, at 16:16, Bernhard Reiter wrote: > > What would someone, e.g. Bruce, > > need to do to remove EAX from the current draft? > Join the IETF openpgp mailing list and say =E2=80=9CI propose to remove E= AX from > the current draft=E2=80=9D. [..]=20 Thanks for explaining. [getting drafts and groups to converge again] > Without some resolution to the fundamental technical sticking point > (whether GCM should be tolerated) I don=E2=80=99t see a viable landing zo= ne at this > time. > > The relevant thread starts here: > https://mailarchive.ietf.org/arch/msg/openpgp/_SjXfSOOtdy20nhVv79NBsDBJTc/ > , it covers pretty much all the bases. Again thanks for the pointer, I'll do some reading. Regards, Bernhard =2D-=20 https://intevation.de/~bernhard =C2=A0 +49 541 33 508 3-3 Intevation GmbH, Osnabr=C3=BCck, DE; Amtsgericht Osnabr=C3=BCck, HRB 18998 Gesch=C3=A4ftsf=C3=BChrer Frank Koormann, Bernhard Reiter --nextPart3495381.Oz5GEdysoT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEvdlX+cT+D9xYPc1tK3ujv5vDpVQFAmRLfeAACgkQK3ujv5vD pVTNhwv+OB3Kw5B9B5acG/pUxhbHacjGrW7aRrhvibYoJhzxBsifoXQ6r60O0D8M /YB68v9m/kp6LAmYNkcpXsWNrfO7gR9UaxaVCW5XsOq8kkVj6RwBvezMYKCqJwuO Pj6XX49M2Ab1VpK89Hoqe8kFj3HHe0uEYs0G5aaFH92DfkA6WKNBCIfCGLBmmIfP SIqIkIoMY3kixf78WzbQbLVsQ4E+YBOIMxx+ARuPNcuNhg29Rg3rf9AkJlc25c6z JuGWLPBreYCr4LNX9QlmqCeKgizwRMPvgm/7Gsb9VTyosmKHf9jGTm/M0ru5cLfN 6CRX5MNWxJmRCfPoGYDve8mk0MTlhB4OHw8ewNGpwb5Oz10wwBTelbt0CEfZpTbB Fx10rPWMyeBvZm8Eu1XYSrU2BHVhQ3fcYbeXof/RDmAStJ2T69UPusIxi7Kaewq4 50XToUf3clihvaz664JTlRgHUnuU67brayrzVcRtxMQqX7nJjcOkMNCEENlHueUR Pf1RM0sa =e1PA -----END PGP SIGNATURE----- --nextPart3495381.Oz5GEdysoT-- --===============8417150722298022737== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnupg-devel mailing list Gnupg-devel@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-devel --===============8417150722298022737==--