RFC 8030: Generic Event Delivery Using HTTP Push
In plain English — editorial summary, not part of the RFC
This document describes a simple protocol for the delivery of real- time events to user agents. This scheme uses HTTP/2 server push.
Document record
- Document ID
- RFC8030
- Published
- December 2016
- Authors
- M. Thomson; E. Damaggio; B. Raymor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 8484DNS Queries over HTTPS (DoH)Current
October 2018
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 7396JSON Merge PatchCurrent
October 2014
- RFC 7386JSON Merge PatchObsoleted
October 2014
- RFC 9749Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web PushCurrent
March 2025
- RFC 8040RESTCONF ProtocolUpdated
January 2017
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?