<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.gilman-wimse-use-cases" target="https://datatracker.ietf.org/doc/html/draft-gilman-wimse-use-cases-00">
   <front>
      <title>Workload Identity Use Cases</title>
      <author initials="E." surname="Gilman" fullname="Evan Gilman">
         <organization>SPIRL</organization>
      </author>
      <author initials="J." surname="Richer" fullname="Justin Richer">
         <organization>Bespoke Engineering</organization>
      </author>
      <author initials="P." surname="Kasselman" fullname="Pieter Kasselman">
         <organization>Microsoft</organization>
      </author>
      <author initials="J. A." surname="Salowey" fullname="Joseph A. Salowey">
         <organization>Venafi</organization>
      </author>
      <date month="August" day="28" year="2023" />
      <abstract>
	 <t>   Workload identity systems like SPIFFE provide a unique set of
   security challenges, constraints, and possibilities that affect the
   larger systems they are a part of.  This document seeks to collect
   use cases within that space, with a specific look at both the OAuth
   and SPIFFE technologies.

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-gilman-wimse-use-cases.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-gilman-wimse-use-cases-00" />
   
</reference>
