From nobody Thu Jun 19 12:52:39 2014 Return-Path: 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 E49941A0415 for ; 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-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 wi9BZhIMih9r for ; 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 ; Thu, 19 Jun 2014 12:52:35 -0700 (PDT) Received: by mail-wi0-f175.google.com with SMTP id r20so9964862wiv.8 for ; 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 10.180.36.241 with SMTP id t17mr9401443wij.38.1403207554588; Thu, 19 Jun 2014 12:52:34 -0700 (PDT) Received: by 10.194.51.134 with HTTP; Thu, 19 Jun 2014 12:52:34 -0700 (PDT) Date: Thu, 19 Jun 2014 12:52:34 -0700 Message-ID: From: Martin Thomson 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 ). Milestones: 2015-05 Send web push protocol draft to the IESG as Proposed Standard From nobody Thu Jun 19 14:26:43 2014 Return-Path: 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 ; 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 ; 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 ; Thu, 19 Jun 2014 14:26:39 -0700 (PDT) Received: by mail-wg0-f49.google.com with SMTP id y10so2815389wgg.8 for ; 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 (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 In-Reply-To: Date: Thu, 19 Jun 2014 22:26:36 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> References: To: Martin Thomson 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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=92m glad to see that reflected here. Dan On 19 Jun 2014, at 20:52, Martin Thomson = 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. >=20 > 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. >=20 >=20 > Charter: >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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 ). >=20 > Milestones: >=20 > 2015-05 Send web push protocol draft to the IESG as Proposed Standard >=20 > _______________________________________________ > Webpush mailing list > Webpush@ietf.org > https://www.ietf.org/mailman/listinfo/webpush From nobody Thu Jun 19 14:35:52 2014 Return-Path: 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 1B0741A0442 for ; Thu, 19 Jun 2014 14:35:51 -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 bOYOHC5pYsjV for ; Thu, 19 Jun 2014 14:35:49 -0700 (PDT) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B5AD1A03F4 for ; Thu, 19 Jun 2014 14:35:49 -0700 (PDT) Received: by mail-wi0-f182.google.com with SMTP id bs8so3539798wib.9 for ; Thu, 19 Jun 2014 14:35:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ymlle6Dno0P8D738AjEBsupRlgCV8hDLbuR/YD0/2KY=; b=yqPmDSYUCEXOtBHxIhCSYogdpNid0MGhJ32tJlDKSNfB3nNR37+JGoLShTkz+0GGb7 QrfSxw0pYsi/OZkAVPLD62RpfLSuXZ+NwKEY05kLSRUP9YIi9WUO9tMPi3GFEktpn1U1 FvjphEPqyoJkY0aOUsuIpS+SukohR9Cz3BzwIHj370BhYZUQ3CRJMSLKCPY67F3PRJur i0i+AoyV+32HJJrFfBdwQ6QXv1XKv67mjxTkE1MvI2sfPE3BEJfHswN85NskIeyXYdCw or1qA8rOQWwnefWNwv9ghpFWOhpyZeHRPYFfFnV1KvtqmcD3FOCp7q+ofejByMW3jtTO zmrA== MIME-Version: 1.0 X-Received: by 10.194.63.46 with SMTP id d14mr7871931wjs.24.1403213748112; Thu, 19 Jun 2014 14:35:48 -0700 (PDT) Received: by 10.194.51.134 with HTTP; Thu, 19 Jun 2014 14:35:47 -0700 (PDT) In-Reply-To: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> References: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> Date: Thu, 19 Jun 2014 14:35:47 -0700 Message-ID: From: Martin Thomson To: Daniel Appelquist Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: http://mailarchive.ietf.org/arch/msg/webpush/gA3ayiK0IbGthYNiHPlo5a-He6c 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2014 21:35:51 -0000 On 19 June 2014 14:26, Daniel Appelquist wrote: > This looks good to me. I think the linkage to w3c webapps push API spec i= s key and I=E2=80=99m glad to see that reflected here. Absolutely. I'd consider this to be the main reason for the working group. We can only really declare success if the protocol works for the API. There may be others who benefit, such as the many developers who might be able to discard redundant implementations of proprietary protocols for doing push for different platforms, but the W3C effort is the main driver here. From miguelg@google.com Thu Jun 19 14:31:15 2014 Return-Path: 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 30D401A03F4 for ; Thu, 19 Jun 2014 14:31:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.029 X-Spam-Level: X-Spam-Status: No, score=-2.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, 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 hOqmUMawgjfR for ; Thu, 19 Jun 2014 14:31:13 -0700 (PDT) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A95A1A028C for ; Thu, 19 Jun 2014 14:31:13 -0700 (PDT) Received: by mail-ie0-f178.google.com with SMTP id rd18so2539347iec.37 for ; Thu, 19 Jun 2014 14:31:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ywJxWL/Z0AOfGBg7IDzZM+OLWzeEaSbJWOWhPZ71kB4=; b=d2W7kc7wriOMEHqD7gA8H2/jD7nkSpBft0rcTdWBLetFL4Pbzkt6MD6WK+/Xrqjz3d a59wVNlD9orz/78Z8vUoJg5uRd8rwgREsxTYqPKgCNo9y44qFGHNBx+g8vIg/i2IXZMX kRHtzD1Z0J2j3958GhlP5rUimy9HMWqGjBaLb10MKyRR9qHJhCbVkYhBhJ583vPLrAdG m+o5a91FPJj31gd6VPOZzsVOMpvJEH+JY93J7MlVEUvSc9gFGA0ow1go7/KMN5xLzHYH LLW7/7g4cWLajXVRNx2ibf/WE+idKIIhdJGGJ7/yNdGfCGT9gAis2zmkcHed0Kq/OGff cwKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ywJxWL/Z0AOfGBg7IDzZM+OLWzeEaSbJWOWhPZ71kB4=; b=GOcnA0J4IvHcojr0fiDL2/kQe62H9+HE08JRUSZZ+AjoxUweq1eKiNOqLt3LNUbumc 6Y7YaoL8fHN7xl+p80rVWxh5Z8lSQrBRDHU9NQ1aJu124QI7pyjK3AP2BGscYQjhaMvg TfRAymQL603nAYdZ6swNEZVVuFqdMEU3QZ3c8GCrCsvxzau+tHLTFTD1AjuwLaJ7q9k1 76ZC+q3+vVbNoHlxcvyd33kLXfZMl3H7f//jA7r0DW8lmR/+K109N50Vv1Qr2A8onr3M VPDcfL95JqOO7+Ix2R0DFJDg+xak/1h/DrXEo+ahwR0O8NsgLzauKEeJFNkGIoaTplMI HLfQ== X-Gm-Message-State: ALoCoQmkjP+QyqDjAKMhNcEkZdkogfAL/p5I8G5icLz6g/j/n2GTG67xHBopg/0xAOSY3yf2n0BB X-Received: by 10.42.79.207 with SMTP id s15mr8929614ick.87.1403213472447; Thu, 19 Jun 2014 14:31:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.163.98 with HTTP; Thu, 19 Jun 2014 14:30:52 -0700 (PDT) In-Reply-To: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> References: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> From: Miguel Garcia Date: Thu, 19 Jun 2014 14:30:52 -0700 Message-ID: To: webpush@ietf.org Content-Type: multipart/alternative; boundary=20cf301af9cd91dd7304fc3718e4 Archived-At: http://mailarchive.ietf.org/arch/msg/webpush/uvwkqnpGcoFPSYimilW9JVo24VE X-Mailman-Approved-At: Thu, 19 Jun 2014 15:39:50 -0700 Cc: Martin Thomson 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2014 21:33:24 -0000 --20cf301af9cd91dd7304fc3718e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This looks good to me too. Thanks for sending it out! On Thu, Jun 19, 2014 at 2:26 PM, Daniel Appelquist wrote: > This looks good to me. I think the linkage to w3c webapps push API spec i= s > key and I=E2=80=99m glad to see that reflected here. > > Dan > > On 19 Jun 2014, at 20:52, Martin Thomson 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 ). > > > > 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 mailing list > Webpush@ietf.org > https://www.ietf.org/mailman/listinfo/webpush > --20cf301af9cd91dd7304fc3718e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This looks good to me too. Thanks for sending it out!


On Thu, Jun = 19, 2014 at 2:26 PM, Daniel Appelquist <appelquist@gmail.com> wrote:
This looks good to me. I think the linkage t= o w3c webapps push API spec is key and I=E2=80=99m glad to see that reflect= ed 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:
>
> =C2=A0 Many applications require continuous access to network communic= ations
> =C2=A0 so that real-time events - such as incoming calls or messages -= can
> =C2=A0 be conveyed (or "pushed") to the user in a timely fas= hion.
> =C2=A0 Uncoordinated use of the network from multiple applications can=
> =C2=A0 contribute to unnecessary use of the network on devices. =C2=A0= For
> =C2=A0 instance, maintaining sessions can dominate costs over the long= term,
> =C2=A0 since events are relatively rare. =C2=A0This is particularly on= erous for
> =C2=A0 battery-powered devices, on which network communication contrib= utes a
> =C2=A0 significant portion of power drain. =C2=A0Each independent sess= ion
> =C2=A0 independently incurs overheads, causing unnecessary resource us= age on
> =C2=A0 devices.
>
> =C2=A0 Several modern computing platforms provide a push notification<= br> > =C2=A0 service that consolidates application events, distributing thos= e
> =C2=A0 events to applications as they arrive. =C2=A0The single session= avoids
> =C2=A0 duplicated overhead costs on devices.
>
> =C2=A0 This working group will develop a protocol that applications ca= n use
> =C2=A0 to request the delivery of application data to a device using a=
> =C2=A0 consolidated push notification service. =C2=A0This work will in= clude the
> =C2=A0 ability to push the same message to multiple devices. =C2=A0The= work may
> =C2=A0 include an exemplar protocol for devices registering with push<= br> > =C2=A0 services.
>
> =C2=A0 This work will be done in collaboration with the W3C Webapps Wo= rking
> =C2=A0 Group, who are developing a Web Push API for use in web applica= tions
> =C2=A0 (see <http://www.w3.org/TR/push-api/>).
>
> Milestones:
>
> =C2=A02015-05 Send web push protocol draft to the IESG as Proposed Sta= ndard
>
> _______________________________________________
> Webpush mailing list
> Webpush@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush

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

--20cf301af9cd91dd7304fc3718e4-- From nobody Thu Jun 19 18:21:11 2014 Return-Path: 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 E705E1A0316 for ; Thu, 19 Jun 2014 18:21:09 -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 oFn1QPochEmc for ; Thu, 19 Jun 2014 18:21:05 -0700 (PDT) Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5868C1A030B for ; Thu, 19 Jun 2014 18:21:05 -0700 (PDT) Received: by mail-pa0-f54.google.com with SMTP id et14so2502753pad.13 for ; Thu, 19 Jun 2014 18:21:05 -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 :content-transfer-encoding:message-id:references:to; bh=iudPyjfQkZOF7tiz0sZda3DI2Cv2E53EHbjH+L94t9U=; b=kFNmXznuf9Y+RuT2bp9uX1YWGMWOpn0e0ap6VdmrlE6JarN1n4Ds8gfuB3jvAvImQQ wq298aQ57Ywx7pRLF6aQ/eGt8cW6BruMuWSbAjv7oAY1Qn7nISQDsutBpNvV/Z1pMHmg OSU+IJ4znjG8QbR6QUeZvpaacH5qvux7H0Kv1UtbKIpAdvTEEdTHo3Q9Hn5DL818rfK7 mMQNdRR/eoldSgcWYWVTdqF7C/HaDdKatly7Rn8Ot2yw8PdJdQgB/CvaFk//X+8KAEv1 0xJ+kYbCvLSEHTfiI8OI83EaP74ceeJcBwZEkUVEYhxgrTp2AIq+jjUwA6Mim3eAnXy+ zBAw== X-Received: by 10.68.173.1 with SMTP id bg1mr234992pbc.13.1403227264929; Thu, 19 Jun 2014 18:21:04 -0700 (PDT) Received: from [192.168.1.100] ([1.130.53.109]) by mx.google.com with ESMTPSA id ix7sm10602808pbd.36.2014.06.19.18.21.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 18:21:04 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: James Winterbottom In-Reply-To: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> Date: Fri, 20 Jun 2014 11:20:56 +1000 Content-Transfer-Encoding: 7bit Message-Id: References: <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com> To: webpush@ietf.org X-Mailer: Apple Mail (2.1878.2) Archived-At: http://mailarchive.ietf.org/arch/msg/webpush/H34e3DvvvqntF_-W25AZXI-eis0 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 01:21:10 -0000 Looks good to me On 20 Jun 2014, at 7:26 am, Daniel Appelquist wrote: