RFC 8292: Voluntary Application Server Identification (VAPID) for Web Push
In plain English — editorial summary, not part of the RFC
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 "vapid" 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.
Document record
- Document ID
- RFC8292
- Published
- November 2017
- Authors
- M. Thomson; P. Beverloo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4686Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)Current
September 2006
- RFC 8332Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) ProtocolCurrent
March 2018
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 6287OCRA: OATH Challenge-Response AlgorithmCurrent
June 2011
- RFC 3008Domain Name System Security (DNSSEC) Signing AuthorityObsoleted
November 2000
- RFC 8301Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM)Current
January 2018
- RFC 8265Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsCurrent
October 2017
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?