IETF protocol work on DKIM PQC, EST, and MoQ

IETF working groups advanced technical proposals on post-quantum email authentication, certificate enrollment channel bindings, and media transport object models. Parallel threads covered agent delegation use cases, Privacy Pass adoption, timestamp authority clarifications, FrodoKEM CMS conventions, and NTPv5 identification fields.

DKIM post-quantum signature evaluation rules

The IETF DKIM working group examined a PQC threat model statement, weighing ML-DSA-44 against composite signatures and defining multiple-signature evaluation rules for a DKIM2 migration path. Participants debated how verifiers should handle mixed classical and post-quantum signatures during transition. The outcome will shape long-term email authentication resilience against quantum threats.

EST channel binding revival for TLS 1.3

The LAMPS working group reopened the dormant RFC 7030 tls-unique issue, seeking a TLS 1.3-compatible channel binding fix or errata. Discussion centered on restoring secure enrollment channel bindings that broke with the newer TLS version. A resolution matters for automated certificate management systems that rely on EST.

MoQ sequential Object ID mandate for caching

The MoQ working group considered requiring sequential Object IDs that start at zero to simplify caching logic and cut unnecessary fetches. Debate addressed subgroup gaps and whether the rule fits varied media use cases. Clearer ID rules would improve efficiency for real-time media delivery over QUIC.

Agentproto use-cases draft narrowing

The agentproto working group narrowed candidate drafts for a use-cases document covering cross-domain agent delegation and recovery. Participants mapped existing practice and deployment models to focus the work. The resulting document will guide interoperable agent protocol design.

Privacy Pass reverse-flow draft adoption path

The Privacy Pass working group discussed next steps for adopting the reverse-flow draft, with the chair noting a possible transfer to a new MOLE working group. Early messages assessed readiness and charter fit. Adoption decisions will determine how reverse-flow privacy tokens proceed in the standards process.

RFC 3161 timestamp authority clarifications

An individual draft in LAMPS proposes EKU and key-reuse clarifications to RFC 3161 following discovery of a cross-protocol attack on timestamp authorities. The update aims to tighten security requirements for TSA deployments. Operators of time-stamping services need the guidance to avoid the identified attack surface.

CMS FrodoKEM conventions call for adoption

LAMPS opened a call for adoption of CMS conventions for the ISO-standardized FrodoKEM algorithm, closing 2026-10-28, and received early positive responses. The draft defines how FrodoKEM keys and ciphertexts fit inside CMS structures. Adoption would expand post-quantum options for CMS-based messaging and storage.

NTPv5 server identification field sizing

NTPv5 draft discussion examined extension field sizing and truncation for server or node identification to limit amplification risk. Participants weighed operational needs against packet-size constraints. Proper bounds help keep NTP deployments resistant to abuse while supporting identification use cases.