<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hardt-email-verification" target="https://datatracker.ietf.org/doc/html/draft-hardt-email-verification-01">
   <front>
      <title>Email Verification Protocol</title>
      <author initials="D." surname="Hardt" fullname="Dick Hardt">
         <organization>Hellō</organization>
      </author>
      <author initials="S." surname="Goto" fullname="Sam Goto">
         <organization>Google</organization>
      </author>
      <date month="July" day="7" year="2026" />
      <abstract>
	 <t>   This document defines the Email Verification Protocol (EVP), the
   HTTP-level protocol by which a browser obtains a signed email
   verification token from an issuer and presents it to a relying party
   (RP).  The protocol enables web applications to verify that a user
   controls an email address without sending a verification email.  It
   uses a three-party model in which the browser intermediates between
   the RP and the issuer, hiding the RP&#x27;s identity from the issuer and
   supporting private, per-RP email addresses to prevent cross-site
   correlation.

   This document covers issuer discovery, the token issuance request,
   the Email Verification Token (EVT) and Key Binding JWT (KB-JWT)
   formats, and token verification.  The browser API — how the user
   selects an email address and how the token is delivered to the RP —
   is defined in the companion W3C Email Verification API
   ([EVP-Browser]).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hardt-email-verification-01" />
   
</reference>
