[OAUTH-WG] Re: OAuth IETF 127 Call for Agenda Items

Wed, 07 Oct 2026 07:32:24 -0700

I would like to talk about using transaction tokens to cross trust domain boundaries in the WIMSE/OAuth joint session. This is a key capability for organizations deploying transaction tokens and a resource server downstream in the chain needing to invoke a service in a different trust domain. The current version of the individual draft can be found here:


The authors will be publishing an update before IETF 127.

Thanks,
George

--
George Fletcher
Practical Identity LLC

On Oct 6, 2026, at 1:54 PM, Rifaat Shekh-Yusef <[email protected]> wrote:


All,

The OAuth working group chairs have requested 2 two-hour meeting slots on the agenda for IETF 127 in San Francisco.
 
In addition, as the intersection between the work of the WIMSE and OAuth working groups becomes increasingly important, 
the chairs of both groups have requested an additional two-hour joint session dedicated to topics that touch both groups. 
For example, transaction tokens are defined as OAuth artifacts but relate directly to workload security.
 
At this time the OAuth chairs are soliciting proposals for both the dedicated OAuth sessions and the joint WIMSE/OAuth session. 
Please send your requests to the mailing list or directly to the chairs, indicating whether your request is for the OAuth session, 
the joint session, or could fit in either session.  

Current working group items and proposals with demonstrated interest from multiple different parties will get priority.
 
Please note that the Internet-Draft submission cut-off is Monday, 2 November 2026 at 23:59 UTC [1]. 
Please ensure that new drafts and updates to existing drafts are published in Datatracker before the deadline.
 
Regards,
 Rifaat and Hannes

_______________________________________________
OAuth mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
OAuth mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to