Re: [Webpush] Proposed charter
Daniel Appelquist <appelquist@gmail.com> Thu, 19 June 2014 21:26 UTC
Return-Path: <appelquist@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C14741A0316 for <webpush@ietfa.amsl.com>; Thu, 19 Jun 2014 14:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYPQuECki4WB for <webpush@ietfa.amsl.com>; Thu, 19 Jun 2014 14:26:40 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0BD41A028C for <webpush@ietf.org>; Thu, 19 Jun 2014 14:26:39 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id y10so2815389wgg.8 for <webpush@ietf.org>; Thu, 19 Jun 2014 14:26:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GIoeI67uzvQyPe8i1RPaE0NkOeJ5S9iw+TgiQGHYCq8=; b=kYVBpvGF7+JrjCZJ/P+Y7IEgsiu1l2MGd//iS10BxJU9axgLadhB5sUgOt0PGqq//G qzxGjco4VhNsh4pZ6GXvuCmtDGIhfihIDrdnHAi5jLIbXTETknbrm1acH75QmJ9uR8sE TcLIF0zzRc0ULGC7aEbbQwi3RSv9A20a9JPWuJ1SWQ11VvHY3bO1BdQdxm6hmQTmZRkP QsrHLbOv+nOlDXzGS6e8XTou5kdOZqLlimtaTVl0L5WTJpc0/pCa8Zn8UT4RXRu4xHpp 57mBiqZpVhl+sJZCGZECzCMaabNkRMmbOH0AoYTmQFgvPplMiKyBCjh6TVmbqa1DCIE4 4uag==
X-Received: by 10.194.2.244 with SMTP id 20mr7693480wjx.26.1403213198365; Thu, 19 Jun 2014 14:26:38 -0700 (PDT)
Received: from [10.0.1.5] (host109-155-4-190.range109-155.btcentralplus.com. [109.155.4.190]) by mx.google.com with ESMTPSA id wp6sm994542wjb.9.2014.06.19.14.26.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 14:26:37 -0700 (PDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Daniel Appelquist <appelquist@gmail.com>
In-Reply-To: <CABkgnnX+=cq0yrqc8agaBvuX9xNwC1OPjzRa_zkE1m8OMNiCTg@mail.gmail.com>
Date: Thu, 19 Jun 2014 22:26:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com>
References: <CABkgnnX+=cq0yrqc8agaBvuX9xNwC1OPjzRa_zkE1m8OMNiCTg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/webpush/M2rV6U7Y2Fbv7bZ8Pwd-qK2KrBY
Cc: webpush@ietf.org
Subject: Re: [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 21:26:41 -0000
This looks good to me. I think the linkage to w3c webapps push API spec is key and I’m glad to see that reflected here. Dan On 19 Jun 2014, at 20:52, Martin Thomson <martin.thomson@gmail.com> wrote: > 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 > 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 > https://www.ietf.org/mailman/listinfo/webpush
- [Webpush] Proposed charter Martin Thomson
- Re: [Webpush] Proposed charter Daniel Appelquist
- Re: [Webpush] Proposed charter Martin Thomson
- Re: [Webpush] Proposed charter Miguel Garcia
- Re: [Webpush] Proposed charter James Winterbottom