Concluded WG Web-Based Push Notifications (webpush)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Web-Based Push Notifications | |
|---|---|---|---|
| Acronym | webpush | ||
| Area | Applications and Real-Time Area (art) | ||
| State | Concluded | ||
| Charter | charter-ietf-webpush-01 Approved | ||
| Document dependencies | |||
| Additional resources | Issue tracker, Wiki | ||
| Personnel | Chairs | Joe Hildebrand, Phil Sorber, Shida Schubert | |
| Area Director | Adam Roach | ||
| Liaison Contacts | Joe Hildebrand, Shida Schubert | ||
| Mailing list | Address | webpush@ietf.org | |
| To subscribe | https://www.ietf.org/mailman/listinfo/webpush | ||
| Archive | https://mailarchive.ietf.org/arch/browse/webpush/ |
Final Charter for Working Group
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 an HTTP-based 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.
The WG will aim to minimize the amount of additional information that is revealed to the push notification service. It must be possible for the application to apply end-to-end security mechanisms so that messages sent via the push notification service cannot be read or modified by the push notification service. The WG will also consider additional privacy protections, including the ability to prevent the push notification service from gleaning other types of information, such as the association between an application and a specific user
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/).
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Send web push encryption draft to IESG as Proposed Standard | |
| Done | Send web push protocol draft to the IESG as Proposed Standard |