[Webpush] Proposed charter

Martin Thomson <martin.thomson@gmail.com> Thu, 19 June 2014 19:52 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id E49941A0415 for <webpush@ietfa.amsl.com>; Thu, 19 Jun 2014 12:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wi9BZhIMih9r for <webpush@ietfa.amsl.com>; Thu, 19 Jun 2014 12:52:36 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7D1F1A0302 for <webpush@ietf.org>; Thu, 19 Jun 2014 12:52:35 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id r20so9964862wiv.8 for <webpush@ietf.org>; Thu, 19 Jun 2014 12:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=c7a7pv0gIyYgCSNNAawQji9myHD510sPv88d/QNJ3F4=; b=EBbG0MRzaZKSRDBNlMpJcMSVle81iSNOCwjouPeqseJFzALW0I+7/gr0xiS+04ve+r ho4Z752SJfBi4PAoeZIwvKi9pdMdoUttBA3pNBIwoDcA4PdtRR70OqA30QarnebAkF9e Ns7W3rT1DxnsV3h3A5p+D99SUfCk9R0Ww9oV/gaWeORPrIat5xVs3WmUmaAB8PncDw3c wVUIg3kKVRKD+jPosL5AXBlE0u2E0/gXzYXysxjsTv2c9GERr7n4Ge/owoe1LQJBlc80 6TGlTlJOQBRsblgT62c6LcO/MyqWxN6TxRH2v8k/OooNJ+fm/e0IIcLnRgIWdyUjLfVJ GwEw==
MIME-Version: 1.0
X-Received: by with SMTP id t17mr9401443wij.38.1403207554588; Thu, 19 Jun 2014 12:52:34 -0700 (PDT)
Received: by with HTTP; Thu, 19 Jun 2014 12:52:34 -0700 (PDT)
Date: Thu, 19 Jun 2014 12:52:34 -0700
Message-ID: <CABkgnnX+=cq0yrqc8agaBvuX9xNwC1OPjzRa_zkE1m8OMNiCTg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: webpush@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/webpush/do29Lhf92-j3lzD4APSwv6gn0d8
Subject: [Webpush] Proposed charter
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2014 19:52:38 -0000

This is the text of the charter that I proposed on dispatch@ietf.org
yesterday in a screaming hurry after discovering that the deadline had

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.


   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

   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

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


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