Re: [Webpush] Proposed charter

Miguel Garcia <miguelg@google.com> Thu, 19 June 2014 21:31 UTC

Return-Path: <miguelg@google.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 30D401A03F4 for <webpush@ietfa.amsl.com>; 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 <webpush@ietfa.amsl.com>; 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 <webpush@ietf.org>; Thu, 19 Jun 2014 14:31:13 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id rd18so2539347iec.37 for <webpush@ietf.org>; 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: <CABkgnnX+=cq0yrqc8agaBvuX9xNwC1OPjzRa_zkE1m8OMNiCTg@mail.gmail.com> <7A8AE65B-6995-45F1-A5F9-692BA8D792F8@gmail.com>
From: Miguel Garcia <miguelg@google.com>
Date: Thu, 19 Jun 2014 14:30:52 -0700
Message-ID: <CAGTrua08XVq9JX=sGv5xv+SfXJyBtaKGzoYH82Gwb8f9LEssDQ@mail.gmail.com>
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 <martin.thomson@gmail.com>
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:33:24 -0000

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 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 mailing list
> Webpush@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush
>