IETF last calls, DKIM2, and TEAS power debates

IETF process advanced several last calls and adoption discussions while working groups argued over DKIM2 design choices and the feasibility of power-aware traffic engineering. Governance, email authentication, OAuth agents, verifiable credentials, and RPKI terminology all saw notable activity.

IESG last call on PR-Action for Ken Kubota

The IESG opened a last call on an RFC 3683 PR-Action that would suspend Ken Kubota's posting rights on the tls, sshm, mod-discuss, and ietf lists. The action targets disruptive unprofessional commentary. List participants and those tracking IETF moderation norms have a direct stake in the outcome.

DKIM WG debates key validity field for DKIM2

The DKIM working group discussed adding a dedicated key validity field to the DKIM2 draft and compared JSON recipes with flat tags. Contributors examined how validity information should be carried. The choice will influence the shape of next-generation email authentication.

OAuth thread on execution-time state binding for agents

An OAuth WG exchange explored a gap in execution-time state binding when agents use Rich Authorization Requests and preconditions across independent resources. The thread focuses on how authorized agent actions can keep consistent state. Developers building agent-driven authorization flows need the gap closed.

Last call for SD-JWT VC to Proposed Standard

The IESG issued a last call for draft-ietf-oauth-sd-jwt-vc-19, which defines SD-JWT-based Verifiable Digital Credentials, seeking advancement to Proposed Standard. Off-list comments are being tracked in the repository. The draft matters for anyone implementing selective-disclosure credential formats.

TEAS dispute over distributed power-aware TE

The TEAS working group debated whether distributed power-aware traffic-engineering path computation is feasible while considering adoption of draft-many-teas-power-steering. Some participants argued that distributed power-aware TE is impossible. The exchange affects the viability of energy-aware path computation designs.

SIDROPS call for adoption of RPKI terminology draft

SIDROPS opened a call for adoption of the informational draft-yan-sidrops-rpki-terminology-05. Discussion covered definitions, ongoing maintenance, and document scope. Consistent RPKI vocabulary supports clearer routing-security specifications.