TLS PQC consensus fights and related protocol work

IETF discussion on 2026-09-26 was dominated by formal complaints against TLS working group handling of post-quantum drafts. Separate threads refined DKIM2 key handling, SMTP confidentiality requirements, and RADIUS over TLS termination text.

Complaint alleges false consensus on ML-KEM draft

D.J. Bernstein complained to the TLS WG chairs that they falsely claimed working group consensus to issue an RFC for draft-ietf-tls-mlkem despite 82 opposing WGLC responses. The chairs locked the thread. The dispute matters because it questions how consensus was recorded for a core post-quantum TLS mechanism.

Charter complaints put ML-DSA and ML-KEM drafts on hold

Bernstein told the area directors that draft-ietf-tls-mldsa and draft-ietf-tls-mlkem violate the TLS working group charter. The RFC Editor placed both documents on Stream Hold pending AD resolution. Implementers waiting on standardized post-quantum TLS algorithms face an immediate process delay.

Jeopardy complaint filed on the same PQC drafts

Bernstein submitted a formal RFC 2026 jeopardy complaint to the ADs against draft-ietf-tls-mldsa and draft-ietf-tls-mlkem. The filing adds another procedural layer to the existing charter and consensus objections. Resolution will determine whether the drafts can advance or must be reworked.

Broader appeal on rough consensus and COI rejected

A complainant escalated allegations of an incorrect rough consensus call, conflict of interest violations, and NSA strategy concerns to the TLS chairs and IESG over the ML-KEM work. The chairs and Security AD rejected the appeal on conduct grounds. The decision leaves the prior consensus determination standing for the moment.

DKIM2 thread weighs key validity tag and format

Participants on the ietf-dkim list debated a proposal to add a key validity field for DKIM2 and whether to use JSON or traditional tag=value encoding. The exchange cited parser ambiguity risks and RFC 7282 consensus rules. Email authentication developers need clarity on the chosen format to avoid interoperability breaks.

Last-call dispute over mandatory TLS in emailcore

A lengthy last-call discussion examined Roman's DISCUSS on draft-ietf-emailcore-as and whether the document should mandate TLS confidentiality for SMTP. Objectors raised concrete use-case problems. The outcome will set the baseline security expectation for the email core architecture.

TLS co-chair replies to ML-KEM consensus complaint

A TLS working group co-chair responded to the allegation of an improper consensus call on draft-ietf-tls-mlkem. The reply directly addresses the procedural claims. It supplies the chairs' official stance for anyone tracking the standardization dispute.

RADIUS/(D)TLS-bis text finalized on terminations

The radext working group completed normative language on connection termination and alerts for rejected clients in the RADIUS/(D)TLS-bis draft. The update moves the document closer to completion. Operators running RADIUS over TLS gain precise rules for handling failed client connections.