<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-webpush-vapid" target="https://datatracker.ietf.org/doc/html/draft-ietf-webpush-vapid-04">
   <front>
      <title>Voluntary Application Server Identification (VAPID) for Web Push</title>
      <author initials="M." surname="Thomson" fullname="Martin Thomson">
         <organization>Mozilla</organization>
      </author>
      <author initials="P." surname="Beverloo" fullname="Peter Beverloo">
         <organization>Google</organization>
      </author>
      <date month="September" day="3" year="2017" />
      <abstract>
	 <t>An application server can use the Voluntary Application Server Identification (VAPID) method described in this document to voluntarily identify itself to a push service.  The &quot;vapid&quot; authentication scheme allows a client to include its identity in a signed token with requests that it makes.  The signature can be used by the push service to attribute requests that are made by the same application server to a single entity.  The identification information can allow the operator of a push service to contact the operator of the application server.  The signature can be used to restrict the use of a push message subscription to a single application server.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-webpush-vapid-04" />
   
</reference>
