Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Generic Event Delivery Using HTTP Push (RFC8030)

IP.com Disclosure Number: IPCOM000248495D
Original Publication Date: 2016-Dec-01
Included in the Prior Art Database: 2016-Dec-09
Document File: 62 page(s) / 68K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Thomson: AUTHOR [+4]

Abstract

Many applications on mobile and embedded devices require continuous access to network communications so that real-time events -- such as incoming calls or messages -- can be delivered (or "pushed") in a timely fashion. These devices typically have limited power reserves, so finding more efficient ways to serve application requirements greatly benefits the application ecosystem.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

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.  Collect...