<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-regext-epp-https" target="https://datatracker.ietf.org/doc/html/draft-ietf-regext-epp-https-04">
   <front>
      <title>Extensible Provisioning Protocol (EPP) Transport over HTTPS</title>
      <author initials="M." surname="Loffredo" fullname="Mario Loffredo">
         <organization>IIT-CNR/Registro.it</organization>
      </author>
      <author initials="L. L." surname="Trombacchi" fullname="Lorenzo Luconi Trombacchi">
         <organization>IIT-CNR/Registro.it</organization>
      </author>
      <author initials="M." surname="Martinelli" fullname="Maurizio Martinelli">
         <organization>IIT-CNR/Registro.it</organization>
      </author>
      <author initials="D." surname="Keathley" fullname="Dan Keathley">
         <organization>VeriSign, Inc.</organization>
      </author>
      <author initials="J." surname="Gould" fullname="James Gould">
         <organization>VeriSign, Inc.</organization>
      </author>
      <date month="September" day="3" year="2026" />
      <abstract>
	 <t>   This document describes how an Extensible Provisioning Protocol (EPP)
   connection is mapped onto the Hypertext Transfer Protocol (HTTP).
   EPP over HTTP (EoH) requires the use of Transport Layer Security
   (TLS) to secure EPP information (i.e. HTTPS).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-regext-epp-https-04" />
   
</reference>
