W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

FYI: IETF Webpush Proposed charter

From: Arthur Barstow <art.barstow@gmail.com>
Date: Tue, 24 Jun 2014 13:34:28 -0400
Message-ID: <53A9B6A4.90908@gmail.com>
To: public-webapps <public-webapps@w3.org>

-------- Original Message --------
Subject: 	Fwd: [Webpush] Proposed charter
Resent-Date: 	Fri, 20 Jun 2014 04:37:30 +0000
Resent-From: 	www-tag@w3.org
Date: 	Thu, 19 Jun 2014 22:37:24 +0100
From: 	Daniel Appelquist <appelquist@gmail.com>
To: 	TAG List <www-tag@w3.org>

FYI - there is a group forming in IETF (WebPush) to work on the protocol 
definition of the web push spec. Its proposed charter (see below) 
specifically calls for collaboration with the push API work in WebApps. 
As weve done some work and coordination on push, and called for some 
work to be done at the protocol level, I though Id bring it to the 
attention of the TAG.

Might make sense to see if we can ask Martin and others working on push 
from various angles to join us on the phone for a portion of our f2f


Begin forwarded message:

> *From: *Martin Thomson <martin.thomson@gmail.com 
> <mailto:martin.thomson@gmail.com>>
> *Subject: **[Webpush] Proposed charter*
> *Date: *19 June 2014 20:52:34 BST
> *To: *webpush@ietf.org <mailto:webpush@ietf.org>
> This is the text of the charter that I proposed on dispatch@ietf.org 
> <mailto:dispatch@ietf.org>
> yesterday in a screaming hurry after discovering that the deadline had
> passed.
> If there is anything here that you'd like to have changed, let's
> discuss that so that I can provide the dispatch chairs with an update.
> Prior to starting a working group, there is plenty of opportunity to
> change and refine language.
> 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 work 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
> _______________________________________________
> Webpush mailing list
> Webpush@ietf.org <mailto:Webpush@ietf.org>
> https://www.ietf.org/mailman/listinfo/webpush
Received on Tuesday, 24 June 2014 17:34:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:25 UTC