IESG
Internet Engineering Steering Group · RFC Ed Queue · RFC Editor queue
Internet Engineering Steering Group: the IETF body that reviews and approves a working group's draft for publication. Once it approves, the draft waits in the RFC Editor's queue for its number; that queue is the last step before a standard is published.
In our briefings
The claim each of the newest briefings on IESG would have you leave with.
In the draft's main flow, a transaction token is minted once, at the edge of a trust domain, and passed on unchanged. The external-facing endpoint exchanges the inbound access token at the transaction token service (TTS) for a short-lived signed JWT. Its sub claim names the transaction's principal, the user or workload it is for, and its txn claim is a unique transaction identifier. Each workload that receives it must check the signature, audience and expiry, and must pass it downstream 'as it was received', in a dedicated Txn-Token header on HTTP calls. No claim is defined as a list of the hops along the way. req_wl is 'A string value that identifies the workload that requested' the token, and although a change-log entry says the authors 'Clarified how multiple workloads are represented in the req_wl claim', the definition says no more. It does allow replacement tokens, while warning that replacing them 'potentially negates the primary purpose of having Txn-Tokens', and a replacement must keep the call chain of the workloads that requested the replaced token, by a mechanism the draft leaves 'out of scope'. We read this as a token that names who a transaction is for and leaves the record of each hop to something else.
Transaction Tokens carry who started a request through internal services and define no list of the hops in betweenBI-FIND-2026-0171
The IETF datatracker shows that the IESG approved OAuth Identity and Authorization Chaining Across Domains (draft-ietf-oauth-identity-chaining) as a Proposed Standard on 22 June 2026, and that it has been in the RFC Editor's queue since that day. Revision 17, the text we read, was posted on 19 July 2026 during that editing. Its authors are Arndt Schwenkschuster and Pieter Kasselman of Defakto Security, Kelley Burgin of MITRE, Mike Jenkins of NSA-CCSS, Brian Campbell of Ping Identity and Aaron Parecki of Okta. Campbell co-wrote RFC 8693 and RFC 7523, the two RFCs the draft combines, and Parecki co-wrote RFC 9728, one of the ways it names for finding the other domain's authorization server. The working group's write-up for the IESG lists implementations, among them Keycloak 26.5 and Okta's. Two other drafts we have read point to it: the transaction-tokens draft leaves crossing domains to it, and the AI agent authentication draft says cross-domain access SHOULD use identity chaining.
OAuth's draft for crossing trust domains is approved for publication and never says agentBI-FIND-2026-0184
Under revision -11 of the bis draft, a JWT that authenticates an OAuth client has exactly one permitted audience. The draft rewrites RFC 7523's rule so that the audience 'MUST use the issuer identifier [RFC8414] of the authorization server as its sole value', 'the token endpoint URL of the authorization server MUST NOT be used as an audience value', and the server 'MUST reject any JWT that does not contain its issuer identifier as its sole audience value'. Unless an application profile says otherwise, the values are compared by Simple String Comparison. The server must have an issuer identifier to use the rule at all, and participants no longer need to agree on audience identifiers for client authentication. Pushed authorization requests (RFC 9126) get the same sole-issuer rule. The draft's reason is that endpoint addresses other than the issuer 'cannot be directly validated' and, sent to a different endpoint, 'can open an attack vector'. It cites the vulnerability University of Stuttgart researchers disclosed to the working group in January 2025, and their paper on audience injection attacks.
The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpointBI-FIND-2026-0350
›Cited in 7 briefings
Every briefing that discusses this term, newest first.
- Transaction Tokens carry who started a request through internal services and define no list of the hops in between
Draft · · IETF OAuth Working Group · Atul Tulshibagwale et al. · Jul 30, 2026
- OAuth's draft for crossing trust domains is approved for publication and never says agent
Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026
- The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpoint
Draft · · IETF Datatracker · Michael B. Jones et al. · Apr 28, 2026
- In SD-JWT VC, the X.509 key route does not authenticate the iss claim
Draft · · IETF Datatracker · Oliver Terbu et al. · Aug 31, 2026
- The IETF's stronger workload proof is built for the proxy in the middle, and it still leaves replay protection optional
Draft · · IETF Datatracker · Joseph A. Salowey et al. · Oct 20, 2026
- OAuth 2.1's October draft bans plain PKCE and adds browser-app rules; 2.1-only clients can fail on older servers
Draft · · IETF Datatracker · Dick Hardt et al. · Mar 2, 2026
- W3C's Controlled Identifiers 1.0 lets an HTTPS URL publish its keys, and whoever can edit that document is its controller
Article · · W3C · Manu Sporny et al. · May 15, 2025