@techreport{mw-oauth-actor-chain-overview-01, number = {draft-mw-oauth-actor-chain-overview-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-mw-oauth-actor-chain-overview/01/}, author = {A Prasad and Ramki Krishnan and Diego Lopez and Srinivasa Addepalli and Suresh Krishnan}, title = {{OAuth Actor Chain: Overview and Design}}, pagetotal = 10, year = 2026, month = nov, day = 1, abstract = {A request can pass through several services before reaching an API. OAuth Token Exchange can represent an actor history in nested act claims. It leaves the rules for constructing that history, limiting its disclosure, and verifying an actor's own signature to additional profiles. Actor Chain proposes those rules while keeping the Authorization Server responsible for issuing tokens and applying policy. This document provides an overview of the authors' Actor Chain proposal, whose Internet-Draft lineage began in SPICE in February 2026. The companion OAuth Actor Chain: Protocol and Interoperability specification continues the existing OAuth draft series and defines wire formats and processing requirements.}, }