RFC 8291 - Message Encryption for Web Push
Published: November 2017
Category: Standards Track
Author: M. Thomson (Mozilla)
ISSN: 2070-1721
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8291.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Contents
- 1. Introduction
- 2. Push Message Encryption Overview
- 3. Push Message Encryption
- 4. Restrictions on Use of "aes128gcm" Content Coding
- 5. Push Message Encryption Example
- 6. IANA Considerations
- 7. Security Considerations
- 8. References
- Appendix A. Intermediate Values for Encryption
- Author's Address
Related Resources
- Official Text: RFC 8291 (TXT)
- Official Page: RFC 8291 DataTracker
- Info: RFC Editor Info