%% You should probably cite draft-zhu-oauth-async-delegation-05 instead of this revision.
@techreport{zhu-oauth-async-delegation-00,
    number =    {draft-zhu-oauth-async-delegation-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-zhu-oauth-async-delegation/00/},
    author =    {Larry Zhu and Sam Currie},
    title =     {{Sender-Constrained Delegation Handle for Asynchronous OAuth 2.0 Identity Chaining}},
    pagetotal = 31,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document defines an extension to OAuth 2.0 Token Exchange {[}RFC8693{]} and the OAuth Identity Chaining draft {[}I-D.ietf-oauth-identity-chaining{]} for delegated workflows that must continue after the end user has gone offline. When a chained access token expires while the end user is unavailable to re-authenticate (for example, to satisfy a multi-factor authentication or a touch-to-engage gesture), the acting client today has no standards- defined way to obtain a refreshed chained token without either widening privileges, breaking the identity chain, or impersonating the user as a service. This specification introduces the "Delegation Handle": a sender-constrained, audience-locked, scope- frozen JSON Web Token issued by the authorization server alongside a chained access token, that the original acting client MAY present back to the authorization server to refresh the chained access token within strict, server-side policy bounds and without re-prompting the end user.},
}