<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.richer-wimse-token-container" target="https://datatracker.ietf.org/doc/html/draft-richer-wimse-token-container-00">
   <front>
      <title>Multi-token Container Data Structure</title>
      <author initials="J." surname="Richer" fullname="Justin Richer">
         <organization>Bespoke Engineering</organization>
      </author>
      <date month="September" day="15" year="2023" />
      <abstract>
	 <t>   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
   https://github.com/bspk/draft-richer-wimse-token-container.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-richer-wimse-token-container-00" />
   
</reference>
