Standards#

IETF 126 (Vienna) — for a networking, security, and identity PM

A standards meeting, so the unit of value is the draft, not the talk. Maturity matters: below, WG-adopted / WGLC documents (BGP-LS BGP-only fabric, EVPN First Hop Security, WIMSE credentials, Merkle Tree Certificates, OAuth-SPIFFE) are the ones closest to changing implementations; the AI-fabric drafts from IDR/RTG/SPRING are mostly early individual drafts but backed by unusually broad operator/vendor coalitions. Two clusters dominate this cycle: AI backend networking (adaptive routing, entropy, lossless WAN) and workload/agentic identity (WIMSE maturing, agent delegation exploding).

IETF 125 (Shenzhen)

A standards meeting: the substance is in the drafts, and the signal is in what is moving toward adoption. This cycle is dominated by two waves: AI/ML Ethernet fabrics (adaptive routing, sub-100µs fast reroute, lossless DCN+WAN flow control, multicast for collectives) and agentic identity (OAuth transaction tokens, delegation chains, SPIFFE client auth, workload identity hints in TLS). Both are moving from individual drafts toward WG adoption.

IETF 124 (Montreal) — Standards

A working-group program, so this digest reads the drafts, not the talks: what is moving toward consensus, what changed in wire formats or security/identity mechanisms, and what is still an individual contribution. The dominant gravity this cycle is AI-fabric networking (FANTEL fast notifications, GLB in Clos fabrics, lossless RDMA over WAN) and a very active workload-identity cluster (WIMSE, SPIFFE–OAuth, transaction tokens).

IETF 123 (Madrid)

A standards meeting, so the unit of work is the Internet-Draft, not the session. This cycle's signal is concentrated in three places that map directly onto your interests: workload identity finally cohering into a full WG-adopted stack (WIMSE), the post-quantum migration moving from algorithm definition into deployment mechanics across TLS/PKIX/COSE/JOSE, and datacenter fabric work in NVO3, RIFT, and SAVNET. Selection is from the program; every write-up below is grounded in the draft abstract only (no paper links were available to enrich from), and is flagged as such.

A note on maturity, since it's the whole game in a standards venue: draft-ietf-* means a working group has adopted the work (it carries weight); draft-<author>-* is an individual submission (early, may go nowhere). Where both exist for the same title, the WG copy is the one to track.

IETF 122 (Bangkok)

Program source is the datatracker documents API, filtered to a curated set of 26 working groups touching cloud-native networking, network security, and identity. As with any standards meeting, the unit of work is the Internet-Draft, not the session — sessions are thin, drafts carry the substance. All write-ups below are grounded in draft abstracts only; no PDF/page links were available in the program text to enrich from, so treat "What/How" as abstract-level, not full-text analysis. draft-ietf-* means a working group has adopted the work (it carries real weight); a bare draft-<author>-* is an individual submission that may or may not go anywhere — noted per item where it matters. Datatracker links are added per draft (https://datatracker.ietf.org/doc/<name>/) since the program text itself carried no reference links.

The headline this cycle: workload identity (WIMSE) has gone from architecture sketch to a nearly-complete, implementable protocol stack, and it's flanked by matching moves in OAuth (cross-domain identity propagation), attestation (RATS), and supply-chain transparency (SCITT) — all converging on the same underlying problem of proving what is talking to what, and on whose behalf.