<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.fletcher-transaction-token-chaining-profile" target="https://datatracker.ietf.org/doc/html/draft-fletcher-transaction-token-chaining-profile-02">
   <front>
      <title>Transaction Token Authorization Grant Profile for OAuth Identity and Authorization Chaining</title>
      <author initials="G." surname="Fletcher" fullname="George Fletcher">
         <organization>Practical Identity LLC</organization>
      </author>
      <author initials="P." surname="Kasselman" fullname="Pieter Kasselman">
         <organization>Defakto Security</organization>
      </author>
      <author initials="S." surname="O&#x27;Dell" fullname="Sean O&#x27;Dell">
         <organization>CVS Health</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   This specification defines a profile of the OAuth Identity and
   Authorization Chaining Across Domains
   [I-D.ietf-oauth-identity-chaining] mechanism that uses a Transaction
   Token (Txn-Token) [I-D.ietf-oauth-transaction-tokens] as the subject
   token in a Token Exchange [RFC8693] request to obtain a JWT
   Authorization Grant for crossing a trust boundary.

   A Txn-Token is scoped to a single trust domain and represents the
   full authorization context of an in-progress transaction, regardless
   of whether that transaction was initiated by a human user calling an
   external API, by an internal system event, or by an automated
   workload.  This profile specifies how a service operating within that
   trust domain can present its Txn-Token to obtain a JWT Authorization
   Grant that carries the necessary context across a trust boundary,
   enabling an access token to be issued for a partner service, without
   exposing internal trust-domain credentials or token formats beyond
   the trust boundary.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-fletcher-transaction-token-chaining-profile-02" />
   
</reference>
