Message Encryption for Web Push
draft-ietf-webpush-encryption-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (webpush WG)
|
|
Last updated |
|
2016-06-29
|
|
Replaces |
|
draft-thomson-webpush-encryption
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group M. Thomson
Internet-Draft Mozilla
Intended status: Standards Track June 29, 2016
Expires: December 31, 2016
Message Encryption for Web Push
draft-ietf-webpush-encryption-03
Abstract
A message encryption scheme is described 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 Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 31, 2016.
Copyright Notice
Copyright (c) 2016 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
(http://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.
Thomson Expires December 31, 2016 [Page 1]
Internet-Draft Web Push Encryption June 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. Key Generation and Agreement . . . . . . . . . . . . . . . . 3
2.1. Diffie-Hellman Group Information . . . . . . . . . . . . 3
2.2. Key Distribution . . . . . . . . . . . . . . . . . . . . 4
2.3. Push Message Authentication . . . . . . . . . . . . . . . 4
3. Message Encryption . . . . . . . . . . . . . . . . . . . . . 4
3.1. Key Derivation . . . . . . . . . . . . . . . . . . . . . 4
3.2. Push Message Content Encryption . . . . . . . . . . . . . 5
4. Message Decryption . . . . . . . . . . . . . . . . . . . . . 6
5. Mandatory Group and Public Key Format . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
The Web Push protocol [I-D.ietf-webpush-protocol] is an intermediated
protocol by necessity. Messages from an Application Server are
delivered to a User Agent via a Push Service.
+-------+ +--------------+ +-------------+
| UA | | Push Service | | Application |
+-------+ +--------------+ +-------------+
| | |
| Setup | |
|<====================>| |
| Provide Subscription |
|-------------------------------------------->|
| | |
: : :
| | Push Message |
| Push Message |<---------------------|
|<---------------------| |
| | |
This document describes how messages sent using this protocol can be
secured against inspection, modification and falsification by a Push
Service.
Web Push messages are the payload of an HTTP message [RFC7230].
These messages are encrypted using an encrypted content encoding
[I-D.ietf-httpbis-encryption-encoding]. This document describes how
Thomson Expires December 31, 2016 [Page 2]
Internet-Draft Web Push Encryption June 2016
this content encoding is applied and describes a recommended key
management scheme.
Show full document text