RE: [Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[SULLIVAN, BRYAN L]

I agree. I'll help get this out the door asap, likely next week.

Thanks,
Bryan Sullivan | Service Standards | AT&T

-Original Message-
From: Arthur Barstow [mailto:art.bars...@gmail.com] 
Sent: Friday, September 26, 2014 5:44 AM
To: Michael van Ouwerkerk; Bryan Sullivan; EDUARDO FULLEA CARRERA
Cc: public-webapps
Subject: Re: [Webpush] IETF proposes new "Web-Based Push Notifications" Working 
Group

On 9/24/14 1:21 PM, Michael van Ouwerkerk wrote:
> The linked working draft is now more than a year old. The latest 
> editor's draft has some inconsistencies while we transition to a 
> service worker based system, but it's much closer to the current 
> discussions:
> https://w3c.github.io/push-api/

Thanks for pointing this out Mike. Since the ED uses respec, it's 
trivial to prepare a new WD for publication.

Bryan, Eduardo - given IETF directly refers to the TR version of Push 
API, I recommend we publish a new WD for Push API? [1] gets us pretty 
close and I can help. OK?

-Thanks, AB

[1] 
<https://w3c.github.io/push-api/?specStatus=WD;publishDate=2014-10-02;previousPublishDate=2013-08-15>

Re: [Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[Peter Beverloo]

On Fri, Sep 26, 2014 at 3:42 PM, Martin Thomson 
 wrote:

> If you would prefer that the IETF wg charter refer to something else,
> please let me know promptly. A small correction is still possible, but the
> window is closing.
>
I think the IETF spec should continue to refer to the latest version
published by the Working Group, so no changes are necessary.

On Fri, Sep 26, 2014 at 1:44 PM, Arthur Barstow 
wrote:

> On 9/24/14 1:21 PM, Michael van Ouwerkerk wrote:
>
>> The linked working draft is now more than a year old. The latest editor's
>> draft has some inconsistencies while we transition to a service worker
>> based system, but it's much closer to the current discussions:
>> https://w3c.github.io/push-api/
>>
>
> Thanks for pointing this out Mike. Since the ED uses respec, it's trivial
> to prepare a new WD for publication.
>
> Bryan, Eduardo - given IETF directly refers to the TR version of Push API,
> I recommend we publish a new WD for Push API? [1] gets us pretty close and
> I can help. OK?


I'm strongly in favor of pushing a new working draft.

Michael and I will work with Eduardo and Bryan to prepare the current ED
for publication late next week. Does that work for you, Arthur?

Thanks,
Peter

Re: [Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[Arthur Barstow]

On 9/26/14 10:42 AM, Martin Thomson wrote:


If you would prefer that the IETF wg charter refer to something else, 
please let me know promptly. A small correction is still possible, but 
the window is closing.




Well, it seems like IETF process would suggest/prescribe what should be 
done. (I don't have a preference here.)


(Regardless, I again recommend WebApps should go ahead and update the 
push-api TR.)


-AB

Re: [Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[Martin Thomson]

If you would prefer that the IETF wg charter refer to something else,
please let me know promptly. A small correction is still possible, but the
window is closing.
On Sep 26, 2014 1:47 PM, "Arthur Barstow"  wrote:

> On 9/24/14 1:21 PM, Michael van Ouwerkerk wrote:
>
>> The linked working draft is now more than a year old. The latest editor's
>> draft has some inconsistencies while we transition to a service worker
>> based system, but it's much closer to the current discussions:
>> https://w3c.github.io/push-api/
>>
>
> Thanks for pointing this out Mike. Since the ED uses respec, it's trivial
> to prepare a new WD for publication.
>
> Bryan, Eduardo - given IETF directly refers to the TR version of Push API,
> I recommend we publish a new WD for Push API? [1] gets us pretty close and
> I can help. OK?
>
> -Thanks, AB
>
> [1]  previousPublishDate=2013-08-15>
>
>

Re: [Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[Arthur Barstow]

On 9/24/14 1:21 PM, Michael van Ouwerkerk wrote:
The linked working draft is now more than a year old. The latest 
editor's draft has some inconsistencies while we transition to a 
service worker based system, but it's much closer to the current 
discussions:

https://w3c.github.io/push-api/


Thanks for pointing this out Mike. Since the ED uses respec, it's 
trivial to prepare a new WD for publication.


Bryan, Eduardo - given IETF directly refers to the TR version of Push 
API, I recommend we publish a new WD for Push API? [1] gets us pretty 
close and I can help. OK?


-Thanks, AB

[1] 

Re: [Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[Michael van Ouwerkerk]

On Wed, Sep 24, 2014 at 3:20 PM, Arthur Barstow 
wrote:

> [ Bcc webp...@ietf.org ]
>
> Hi All,
>
> I recall the IETF's intent to create a web-based push notifications
> protocol standard was previously announced on this list. Please note the
> draft charter for this WG explicitly mentions WebApps:
>
> [[
> 
>

I think it will be very valuable to have a standardized push server
protocol.


>
> ...
>
> 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
> ).
> ]]
>

The linked working draft is now more than a year old. The latest editor's
draft has some inconsistencies while we transition to a service worker
based system, but it's much closer to the current discussions:
https://w3c.github.io/push-api/

I invite you all to contribute to the issues on the github project:
https://github.com/w3c/push-api/issues

I'm happy to continue making and reviewing pull requests. Again, additional
contributors are very welcome!

Regards,

Michael


>
> If anyone has any comments or concerns about this, please speak up.
>
> -Thanks, AB
>
>  Original Message 
> Subject:[Webpush] WG Review: Web-Based Push Notifications (webpush)
> Date:   Wed, 24 Sep 2014 06:19:19 -0700
> From:   The IESG 
> To: IETF-Announce 
> CC: webpush WG 
>
>
>
> A new IETF working group has been proposed in the Real-time Applications
> and Infrastructure Area. The IESG has not made any determination yet. The
> following draft charter was submitted, and is provided for informational
> purposes only. Please send your comments to the IESG mailing list (iesg
> at ietf.org) by 2014-10-01.
>
> Web-Based Push Notifications (webpush)
> 
> Current Status: Proposed WG
>
> Assigned Area Director:
>   Alissa Cooper 
>
> Mailing list
>   Address: webp...@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/webpush
>   Archive:
> http://www.ietf.org/mail-archive/web/webpush/current/maillist.html
>
> Charter:
>
> Many applications require continuous access to network communications so
> that real-time events - such as incoming calls or messages - can be
> conveyed ("pushed") to the user in a timely fashion. Uncoordinated use
> of the network by multiple applications can contribute to unnecessary
> use of the network on devices.  For instance, maintaining sessions can
> dominate costs over the long term, since pushed events are relatively
> rare.  This is particularly onerous for battery-powered devices, on
> which network communication contributes a significant proportion of
> power usage.  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 data to a device using a consolidated push
> notification service. This protocol will include the ability to push the
> same message to multiple subscribed devices.  The work may describe a
> protocol that allows a device to subscribe to a push service and receive
> pushed messages.
>
> 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 ).
>
> Milestones:
>   Nov 2015 - Send web push protocol draft to the IESG as Proposed
> Standard
>
>
> ___
> Webpush mailing list
> webp...@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush
>
>
>
>
>

[Webpush] IETF proposes new "Web-Based Push Notifications" Working Group

[Arthur Barstow]

[ Bcc webp...@ietf.org ]

Hi All,

I recall the IETF's intent to create a web-based push notifications 
protocol standard was previously announced on this list. Please note the 
draft charter for this WG explicitly mentions WebApps:


[[


...

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
).
]]

If anyone has any comments or concerns about this, please speak up.

-Thanks, AB

 Original Message 
Subject:[Webpush] WG Review: Web-Based Push Notifications (webpush)
Date:   Wed, 24 Sep 2014 06:19:19 -0700
From:   The IESG 
To: IETF-Announce 
CC: webpush WG 



A new IETF working group has been proposed in the Real-time Applications
and Infrastructure Area. The IESG has not made any determination yet. The
following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list (iesg
at ietf.org) by 2014-10-01.

Web-Based Push Notifications (webpush)

Current Status: Proposed WG

Assigned Area Director:
  Alissa Cooper 

Mailing list
  Address: webp...@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/webpush
  Archive:
http://www.ietf.org/mail-archive/web/webpush/current/maillist.html

Charter:

Many applications require continuous access to network communications so
that real-time events - such as incoming calls or messages - can be
conveyed ("pushed") to the user in a timely fashion. Uncoordinated use
of the network by multiple applications can contribute to unnecessary
use of the network on devices.  For instance, maintaining sessions can
dominate costs over the long term, since pushed events are relatively
rare.  This is particularly onerous for battery-powered devices, on
which network communication contributes a significant proportion of
power usage.  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 data to a device using a consolidated push
notification service. This protocol will include the ability to push the
same message to multiple subscribed devices.  The work may describe a
protocol that allows a device to subscribe to a push service and receive
pushed messages.

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

Milestones:
  Nov 2015 - Send web push protocol draft to the IESG as Proposed
Standard


___
Webpush mailing list
webp...@ietf.org
https://www.ietf.org/mailman/listinfo/webpush