Skip to main content

Multi-token Container Data Structure

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Justin Richer
Last updated 2024-03-18 (Latest revision 2023-09-15)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


In many use cases, particularly in workload environments, a single access token or similar security artifact is not sufficient for conveying the type of security and provenance information necessary. This draft describes a data model and format for an additive data container to address these concerns. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at


Justin Richer

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)