RFC 9749: Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push
In plain English — editorial summary, not part of the RFC
This document defines a method for JSON Meta Application Protocol (JMAP) servers to advertise their capability to authenticate Web Push notifications using the Voluntary Application Server Identification (VAPID) protocol.
Document record
- Document ID
- RFC9749
- Published
- March 2025
- Authors
- D. Gultsch
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8030Generic Event Delivery Using HTTP PushCurrent
December 2016
- RFC 9755IMAP Support for UTF-8Current
March 2025
- RFC 9741Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of TextCurrent
March 2025
- RFC 9738IMAP MESSAGELIMIT ExtensionCurrent
March 2025
- RFC 9795Personal Assertion Token (PASSporT) Extension for Rich Call DataCurrent
July 2025
- RFC 9796SIP Call-Info Parameters for Rich Call DataCurrent
July 2025
- RFC 9698The JMAPACCESS Extension for IMAPCurrent
January 2025
- RFC 9695The 'haptics' Top-Level Media TypeUpdated
March 2025
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?