Generic Event Delivery Using HTTP Push
RFC 8030
|
| Document |
Type |
|
RFC - Proposed Standard
(December 2016; No errata)
|
|
Last updated |
|
2016-12-08
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Shida Schubert
|
|
Shepherd write-up |
|
Show
(last changed 2016-09-18)
|
| IESG |
IESG state |
|
RFC 8030 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alissa Cooper
|
|
Send notices to |
|
"Shida Schubert" <shida@ntt-at.com>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) M. Thomson
Request for Comments: 8030 Mozilla
Category: Standards Track E. Damaggio
ISSN: 2070-1721 B. Raymor, Ed.
Microsoft
December 2016
Generic Event Delivery Using HTTP Push
Abstract
This document describes a simple protocol for the delivery of real-
time events to user agents. This scheme uses HTTP/2 server push.
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
http://www.rfc-editor.org/info/rfc8030.
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, et al. Standards Track [Page 1]
RFC 8030 HTTP Web Push December 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions and Terminology . . . . . . . . . . . . . . . 4
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. HTTP Resources . . . . . . . . . . . . . . . . . . . . . 7
3. Connecting to the Push Service . . . . . . . . . . . . . . . 8
4. Subscribing for Push Messages . . . . . . . . . . . . . . . . 8
4.1. Collecting Subscriptions into Sets . . . . . . . . . . . 9
5. Requesting Push Message Delivery . . . . . . . . . . . . . . 10
5.1. Requesting Push Message Receipts . . . . . . . . . . . . 10
5.2. Push Message Time-To-Live . . . . . . . . . . . . . . . . 11
5.3. Push Message Urgency . . . . . . . . . . . . . . . . . . 13
5.4. Replacing Push Messages . . . . . . . . . . . . . . . . . 14
6. Receiving Push Messages for a Subscription . . . . . . . . . 15
6.1. Receiving Push Messages for a Subscription Set . . . . . 17
6.2. Acknowledging Push Messages . . . . . . . . . . . . . . . 18
6.3. Receiving Push Message Receipts . . . . . . . . . . . . . 19
7. Operational Considerations . . . . . . . . . . . . . . . . . 20
7.1. Load Management . . . . . . . . . . . . . . . . . . . . . 20
7.2. Push Message Expiration . . . . . . . . . . . . . . . . . 20
7.3. Subscription Expiration . . . . . . . . . . . . . . . . . 21
7.3.1. Subscription Set Expiration . . . . . . . . . . . . . 21
7.4. Implications for Application Reliability . . . . . . . . 22
7.5. Subscription Sets and Concurrent HTTP/2 Streams . . . . . 22
8. Security Considerations . . . . . . . . . . . . . . . . . . . 22
8.1. Confidentiality from Push Service Access . . . . . . . . 23
8.2. Privacy Considerations . . . . . . . . . . . . . . . . . 23
8.3. Authorization . . . . . . . . . . . . . . . . . . . . . . 24
8.4. Denial-of-Service Considerations . . . . . . . . . . . . 25
8.5. Logging Risks . . . . . . . . . . . . . . . . . . . . . . 25
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
9.1. Header Field Registrations . . . . . . . . . . . . . . . 26
9.2. Link Relation URNs . . . . . . . . . . . . . . . . . . . 26
9.3. Service Name and Port Number Registration . . . . . . . . 28
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
10.1. Normative References . . . . . . . . . . . . . . . . . . 28
10.2. Informative References . . . . . . . . . . . . . . . . . 30
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
Thomson, et al. Standards Track [Page 2]
RFC 8030 HTTP Web Push December 2016
Show full document text