WG Review: Web-Based Push Notifications (webpush)

The IESG <iesg-secretary@ietf.org> Wed, 24 September 2014 13:19 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010321A00FC; Wed, 24 Sep 2014 06:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5qus9HcYagS; Wed, 24 Sep 2014 06:19:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCE81A00D6; Wed, 24 Sep 2014 06:19:19 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Web-Based Push Notifications (webpush)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140924131919.8882.85143.idtracker@ietfa.amsl.com>
Date: Wed, 24 Sep 2014 06:19:19 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/lE4lGt-gt1KVhwQNabN30iuV_zY
Cc: webpush WG <webpush@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2014 13:19:21 -0000

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 <alissa@cooperw.in>

Mailing list
  Address: webpush@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 <http://www.w3.org/TR/push-api/>).

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