Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

M. Thomson
P. Beverloo

Stream:

IETF

Source:

webpush (art)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8292

Discuss this RFC: Send questions or comments to the mailing listwebpush@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8292

Abstract

An application server can use the Voluntary Application ServerIdentification (VAPID) method described in this document tovoluntarily identify itself to a push service. The "vapid"authentication scheme allows a client to include its identity in asigned token with requests that it makes. The signature can be usedby the push service to attribute requests that are made by the sameapplication server to a single entity. The identificationinformation can allow the operator of a push service to contact theoperator of the application server. The signature can be used torestrict the use of a push message subscription to a singleapplication server.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.