<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-acme-authority-token" target="https://datatracker.ietf.org/doc/html/draft-ietf-acme-authority-token-09">
   <front>
      <title>Automated Certificate Management Environment (ACME) Challenges Using an Authority Token</title>
      <author initials="J." surname="Peterson" fullname="Jon Peterson">
         <organization>Neustar, Inc.</organization>
      </author>
      <author initials="M." surname="Barnes" fullname="Mary Barnes">
         <organization>Neustar, Inc.</organization>
      </author>
      <author initials="D." surname="Hancock" fullname="David Hancock">
         <organization>Comcast</organization>
      </author>
      <author initials="C." surname="Wendt" fullname="Chris Wendt">
         <organization>Somos</organization>
      </author>
      <date month="October" day="24" year="2022" />
      <abstract>
	 <t>Some proposed extensions to the Automated Certificate Management Environment (ACME) rely on proving eligibility for certificates through consulting an external authority that issues a token according to a particular policy.  This document specifies a generic Authority Token Challenge for ACME that supports subtype claims for different identifiers or namespaces that can be defined separately for specific applications.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-acme-authority-token-09" />
   
</reference>
