Key Themes and Supporting Quotes
| Theme | Summary | Representative Quote |
|---|---|---|
| 1. IETF consensus is being contested – many users argue that DJB is deliberately mis‑labeling “rough consensus” as “voting” to undermine the process. | Critics see this as a tactic to delegitimize IETF decisions and sow distrust. | eqvinox: “DJB keeps calling the IETF consensus process ‘voting’. That’s detrimental to his own case; when there is a vote, the vote can be manipulated.” |
| 2. Need for a formal IETF/RFC specification of pure ML‑KEM – the discussion hinges on whether the working group should publish an RFC to register the code points and describe how TLS can use pure ML‑KEM. | Without an RFC, the spec relies only on external standards (e.g., FIPS‑203) and may hinder interoperability. | eqvinox: “The crux of this is the codepoint allocation in the named group registry. … ‘Specification Required’ … does not mean IETF consensus.” |
| 3. DJB as a polarising, agit‑provocateur figure – several participants point out that Bernstein (DJB) has a history of fighting with IETF groups and now is actively mobilising the community against the draft. | This behaviour is viewed as “brigading” and as attempts to skew perception of the IETF’s processes. | tptacek: “He famously doesn’t support the IETF. … he’s been picking fights like this with different IETF working groups for basically his entire career.” |
All quotations are reproduced verbatim, with HTML entities corrected, and are attributed to the original authors using double‑quoted text.