I support adoption of the draft with or without an applicability statement.
I do not see merit (or even consistency) in the arguments raised about
prioritisation or that code points can simply be registered.
I also see the arguments that certain individuals don't see a need for this
as not at all
Many protocols use mutual authentication within TLS.
One such protocol is KMIP - Key Management Interoperability Protocol - see
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=kmip
In KMIP mutual authentication at the TLS level is mandatory.
I don't get the rationale for Google wanting
On Fri, Mar 7, 2025 at 7:01 PM Kris Kwiatkowski wrote:
> May I know if you have a plan for FIPS certificaton for PQC after release?
>
Absolutely - OpenSSL-3.5 will be heading into a fresh FIPS140-3 validation
in April once the release is final - and that will include the PQC
algorithms that have
On Thu, Mar 6, 2025 at 11:30 PM John Mattsson wrote:
> Great that X25519MLKEM768 and MLKEM1024 will be in the 3.5 LTS release
> https://openssl-library.org/post/2025-02-04-release-announcement-3.5/
>
> Also great to see DTLS 1.3 as a top priority for 3.6.
>
> https://openssl-communities.org/d/HCd
