[dispatch] Charter Proposal: Web Push

Martin Thomson <martin.thomson@gmail.com> Wed, 18 June 2014 19:32 UTC

MIME-Version: 1.0
Date: Wed, 18 Jun 2014 12:32:44 -0700
Message-ID: <CABkgnnVp-Toq5PUX3tFsjT2hDJmNey+QZ727XfiE9iw5fF8fjA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: dispatch.chairs@tools.ietf.org, dispatch@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/Ez0d_3HZxUjEUc1jd5fTdOMHl6Y
Cc: Doug Turner <dougt@mozilla.com>
Subject: [dispatch] Charter Proposal: Web Push
Precedence: list

I notice that the deadlines have been added to the wiki [1], and we're
already past them.  I didn't see any announcement, so I apologize for
being a little late with this request.

We don't believe that this work is enough to need a full BOF, only a
short time in a dispatch session.  We'd like to request that time now.

Charter:

   Many applications require continuous access to network communications
   so that real-time events - such as incoming calls or messages - can
   be conveyed (or "pushed") to the user in a timely fashion.
   Uncoordinated use of the network from multiple applications can
   contribute to unnecessary use of the network on devices.  For
   instance, maintaining sessions can dominate costs over the long term,
   since events are relatively rare.  This is particularly onerous for
   battery-powered devices, on which network communication contributes a
   significant portion of power drain.  Each independent session
   independently incurs overheads, causing unnecessary resource usage on
   devices.

   Several modern computing platforms provide a push notification
   service that consolidates application events, distributing those
   events to applications as they arrive.  The single session avoids
   duplicated overhead costs on devices.

   This working group will develop a protocol that applications can use
   to request the delivery of application data to a device using a
   consolidated push notification service.  This protocol will include the
   ability to push the same message to multiple devices.  The work may
   include an exemplar protocol for devices registering with push
   services.

   This work will be done in collaboration with the W3C Webapps Working
   Group, who are developing a Web Push API for use in web applications
   (see <http://www.w3.org/TR/push-api/>).

Milestones:

  2015-05 Send web push protocol draft to the IESG as Proposed Standard

[dispatch] Charter Proposal: Web Push Martin Thomson
Re: [dispatch] Charter Proposal: Web Push Mary Barnes