Email TLS, DKIM2 keys, and power-aware TE debates

IETF lists on 2026-09-25 centered on email transport security requirements, DKIM2 key lifecycle design, and challenges to distributed power-aware traffic engineering. Process disputes around TLS consensus and new DNS delegation proposals also generated extended technical traffic.

Emailcore applicability statement and TLS requirements

A last-call thread on draft-ietf-emailcore-as produced 84 messages from 22 participants after a DISCUSS from Roman. The debate turns on whether the applicability statement may let servers require TLS or must keep accepting plaintext for backward compatibility. The outcome sets encryption baselines that SMTP implementers and operators will have to meet.

DKIM2 key validity field and encoding

The ietf-dkim list saw 120 messages from 16 participants on a proposal to add a key validity field for DKIM2. Discussion focused on JSON versus traditional tag=value format, parser ambiguity, and RFC 7282 consensus rules. Next-generation DKIM implementers need stable lifetime controls and unambiguous key records.

Distributed power-aware TE feasibility

Aijun Wang challenged the feasibility of distributed power-aware traffic engineering in draft-many-teas-power-steering-01 on the teas list, while authors defended metric-modified CSPF and power groups. The exchange ran to 82 messages from 11 participants after the adoption call closed. Operators tracking energy-aware path computation require resolution of these technical objections.

DELEXT delegation type ranges

DELEG and DELEXT authors proposed four delegation type ranges that govern NS inclusion and referral behavior. Eleven participants examined the semantics and resolver implications across 26 dnsop messages. The ranges will shape how authoritative servers hand off zones and how resolvers interpret new delegation signals.

TLS list process and ML-KEM consensus

Fifteen participants exchanged 28 messages on transparency, moderation, and rough consensus handling for the ML-KEM RFC decision, citing RFCs and involving thread locking. A separate formal complaint to the TLS chairs and IESG alleged improper consensus claims, conflict-of-interest violations, and NSA strategy concerns; chairs declined it on conduct grounds. Post-quantum TLS work depends on clear process outcomes for algorithm selection.

mDNS conflict reporting for ULD

The dnssd list discussed mDNS conflict reporting and naming conventions for the ULD specification in 17 messages from six participants. Reliable local discovery naming hinges on how conflicts are signaled and resolved.

PLANTS MTC use-cases adoption call

A call for adoption of draft-gray-plants-mtc-deploy-use-cases-01, closing 2026-10-02, drew 19 messages from 13 participants on scope and fit for private and WebPKI mutual TLS scenarios. Adoption would fix how MTC deployment cases are documented for implementers.