IETF SSH hybrids, TLS process fights, and protocol proposals

IETF working groups spent the day on post-quantum cryptography choices for SSH and TLS, with sharp process disputes in the latter and smaller proposals advancing elsewhere. Debates centered on balancing compliance pressures against protocol simplicity while adoption calls and vocabulary requests moved forward in related areas.

Hybrid ML-DSA signatures for SSH

The SSH working group examined a draft on hybrid signatures and whether to expand the set of ML-DSA combination options. Participants debated the trade-off between meeting external compliance demands and preserving a minimal protocol design. Implementers of quantum-resistant SSH need to track which combinations survive, as the outcome will constrain authentication code paths.

Contested rough consensus on TLS ML-KEM

TLS working group chairs declared rough consensus on an ML-KEM RFC, prompting immediate pushback on the mailing list. Critics objected to undisclosed weighting given to designated expert participants and to the overall lack of transparency in the call. The dispute matters because it directly affects how post-quantum key-exchange standards are finalized and who can influence them.

SSH certificate draft sizing and scope

Discussion of draft-ietf-sshm-cert in the SSH working group included a concrete suggestion to hash CA keys in order to manage ML-DSA public-key sizes. An unrelated ZTID proposal raised in the same thread was rejected as out of scope. Developers working on SSH certificate extensions should note both the size-mitigation approach under consideration and the firm boundary the group is drawing around the draft.

AI-control inference vocabulary dispute

A publisher proposed new "AI System Inference" and "AI User Input" categories for the IETF AI-Control working group's vocabulary. An implementer challenged both the chosen terminology and the intended scope of the additions. The exchange will shape the control primitives available to protocol designers who must signal AI-related processing constraints.

IPv6 resolved-gateway adoption call

The int-area working group opened a call for adoption of draft-vanmook-intarea-ipv6-resolved-gateway-01, closing 2026-08-21. The document specifies how IPv4 traffic can traverse IPv6-only segments by using a sentinel gateway address taken from the neighbor-discovery cache. Operators running mixed IPv4/IPv6 environments have a limited window to review the mechanism before the adoption decision.