Subject: [Wimse] Token Translation Requirements
From: Justin Richer <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Mon, 29 Jul 2024 12:26:49 +0000
List-Id: WIMSE Workload Identity in Multi-Service Environment <wimse.ietf.org>

Following discussion in Vancouver, the chairs would like to begin discussion on what the next steps should be for the Token Translation Requirements document [1], an output of the Token Exchange Design Team. This is not a call for adoption as there was a clear indication in the room that the document was not yet ready for this stage.

As this is a requirements document, and it is unusual for a requirements document to be codified as an RFC, the chairs would like the group to discuss what the intended direction of this document should be. Please reply to the list to indicate that:

A: You believe this document should be developed into a state that the WG can adopt it. (Please discuss what you believe would be required changes for this. Please keep in mind that a call for adoption is a starting point for a document, not a finished document.)

B: You believe this document should be developed by the WG as something other than a WG / RFC-track document. (Please discuss what you think the right format or forum would be - a wiki page, a web page, an eternal I-D, a blog post, etc)

C: You believe this document should NOT be developed further by the WG. (Please indicate why if possible)

D: You need more information before making this decision. (Please indicate what information you’d need)

D: You don’t give a flying rat about this document (i.e., this is not a topic you care strongly about)

Please reply to the list by August 12th, 2024.

— Justin and Pieter

[1] https://datatracker.ietf.org/doc/draft-rosomakho-wimse-tokentranslation-reqs/