RFC 8291: Message Encryption for Web Push
In plain English — editorial summary, not part of the RFC
This document describes a message encryption scheme for the Web Push protocol. This scheme provides confidentiality and integrity for messages sent from an application server to a user agent.
Document record
- Document ID
- RFC8291
- Published
- November 2017
- Authors
- M. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- 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 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 8765DNS Push NotificationsCurrent
June 2020
- RFC 7540Hypertext Transfer Protocol Version 2 (HTTP/2)Obsoleted
May 2015
- RFC 9113HTTP/2Current
June 2022
- RFC 2617HTTP Authentication: Basic and Digest Access AuthenticationObsoleted
June 1999
- RFC 2084Considerations for Web Transaction SecurityCurrent
January 1997
- RFC 1945Hypertext Transfer Protocol -- HTTP/1.0Current
May 1996
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?