<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.gould-regext-auth-token" target="https://datatracker.ietf.org/doc/html/draft-gould-regext-auth-token-00">
   <front>
      <title>Extensible Provisioning Protocol (EPP) Authentication Token Mapping</title>
      <author initials="J." surname="Gould" fullname="James Gould">
         <organization>VeriSign, Inc.</organization>
      </author>
      <author initials="8. 7. 7. 7. 6. 7. 3. 7. 6. 8." surname="Garg" fullname="Poonam Garg">
         <organization>VeriSign, Inc.</organization>
      </author>
      <author initials="M. S. M." surname="Khader" fullname="Mohammad Suhale Malang Khader">
         <organization>VeriSign, Inc.</organization>
      </author>
      <date month="July" day="20" year="2026" />
      <abstract>
	 <t>   This document describes an Extensible Provisioning Protocol (EPP)
   mapping for provisioning and management of EPP Authentication Token
   objects in a shared central repository, where an Authentication Token
   is a JSON Web Signature (JWS), defined in RFC 7515, and is used to
   authorize actions by registrar users.  The Authentication Token can
   be passed over an authenticated EPP session, as defined in RFC 5730,
   to provide elevated, fine-grained authorization exclusively valid
   until the lifetime of the digitally signed Authentication Token.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-gould-regext-auth-token-00" />
   
</reference>
