[TLS] Complaints/Appeals Response (was: Re: WG Last Call : draft-ietf-tls-mlkem-08 (Ends 2026-07-08))

D. J. Bernstein,

We are acknowledging receipt of two complaints from [1], which did appear on the list. The numbering below is based on the numbering included in your original email. Apologies for not getting to these sooner, as they were only discovered during our review of the ML-KEM working group last call.

On Point #7, the “jeopardy claim” that pure PQ, as opposed to hybrid and regardless of whether it is ML-DSA or ML-KEM, is a ‘technical error’ appears to be based on implementers producing flawed code. Therefore, the damage statements are aspirational at best; there is no way to predict CVEs or lawsuits, let alone ransomware. In fact, your damage assertions could be made about any cipher suite, including existing cipher suites. Finally, your complaint fails to suggest a remedy, but we will assume, based on the other pure PQ-related complaints, that you wish to reject/eject the Internet-Draft from the WG.

As ML-KEM and ML-DSA meet the security goals of FIPS 203 and 204, respectively, the chairs decline the complaint/appeal.

On Point #8, the charter complaint refers to two of the three “goals” of the WG. The third goal, which you mentioned in your original email from November but failed to quote in its entirety, specifically places ciphers suites in scope; see the following:

     The third goal is to maintain current and previous version of
     the (D)TLS protocol as well as to specify general best practices
     for use of (D)TLS, extensions to (D)TLS, and cipher suites.

Lacking a remedy, again, we will assume that you wish to reject/eject the Internet-Draft from the WG. In reviewing all words in the charter, we do not see a charter violation.

If you wish to elevate these complaints further, please direct them to the responsible Security Area Director available at [email protected].

Joe and Sean

[1] https://mailarchive.ietf.org/arch/msg/tls/GL9oPGn60Oz601--gqCk4hcQlCM/

… snip

_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]