[TLS] Re: Fwd: New Version Notification for draft-yusef-tl s-pqt-dual-certs-02.txt

Stephen Farrell <[email protected]> Wed, 15 Jul 2026 20:22:29 +0100
Newsgroups gmane.ietf.tls
Message-ID <[email protected]>
Hiya,

The original comment may have been somewhat mis-directed but I
wanted to react to this nonetheless:

On 15/07/2026 17:59, Erwin Hoffmann wrote:
> 
> Thus, my argumentation is: In order to give a valid guidance, one has
> to consider generation, transport, and usage of those certificates.
> I would call this a 360 degree view.

The above ignores (or at least doesn't call out) TLS server handling of
private keys and certificates. I think that makes a difference for the
dual vs composite situations. I also think we'd (the TLS WG) be wise to
pay attention to server package maintainers on that topic. (Which is not
the same as paying attention to those who operate the most commonly used
servers.) I'm not sure myself what, if any, preferences they might have,
but many of them will have to make changes, if whatever PQ auth solution
is to work for the vast majority of TLS servers. (Which I assume is a
goal.)

Cheers,
S.

_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]
OpenPGP_signature.asc (application/pgp-signature, 236 B)
-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQQwbnhHy1kPJkWsM6fk2On5l6gz3QUCalfd9QUDAAAAAAAKCRDk2On5l6gz3Sdb
AQDDADY/lif4VFtDEHpz5y/X3ozYmsVmPaGG25YeUC4gxAEA9TvUs1ktcXFkL0Idv101dBNdgBGR
+IzuW1q7dMDG4gY=
=5OnM
-----END PGP SIGNATURE-----