IETF Logo Mail Archive

Re: [Webpush] Polling to adopt VAPID draft

Benjamin Bangert <bbangert@mozilla.com> Wed, 06 April 2016 03:09 UTC

Return-Path: <bbangert@mozilla.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AB512D7BD for <webpush@ietfa.amsl.com>; Tue, 5 Apr 2016 20:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mozilla-com.20150623.gappssmtp.com
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 7DmvgyFWIbHE for <webpush@ietfa.amsl.com>; Tue, 5 Apr 2016 20:09:30 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5A2712DA02 for <webpush@ietf.org>; Tue, 5 Apr 2016 19:54:48 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id d68so40623168ywe.1 for <webpush@ietf.org>; Tue, 05 Apr 2016 19:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=WPM+lOr1zIbJBIz0U2wlDqdqQ1hL4yZCL4WThumqmkU=; b=rB9oKgDW9P7+OGNl8HwHM6W01rm7LH4jR+Xjuft715m3xQep3JV4G3LpsThs4psqR7 WVvmti7k8xXAVR3rceL0Y7efcw/lmWkxcHa2a724LISaUhgd2G5NY6wsYRlAWwss0lY/ aHm4nWhTQyIRyu3L00LYwWZetfEuJMLcQFUCnDxSoW6LIGFoQiVvJGL4wq/i/Xps+NDm bFcQcb77wFh8YpJB8wNFhyEM2VDSOlTQAdjgsCwnMPOkowT4/arZIjgyY+AkNMek9b5q qR3VkIJgol4u5meIINIv7Q6wrlyvVwim1tUd0aWdOZQmmA3oHPyEEQaQ4GkkQfpUHKle PN6w==
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:date :message-id:subject:from:to:cc; bh=WPM+lOr1zIbJBIz0U2wlDqdqQ1hL4yZCL4WThumqmkU=; b=gc+SKSqEYgE8oiVG5ZqWVStqB8kpMczh1duxVEX1kSwSZZQn1STUmoS87fWgBo8Xr5 PTjVAvIx6qt/QDY8h6TjA0rPkGwifxefi9XcrvG6dvZ2ebiGQkT1BKRgNrvx8wKqe7j9 KWGQ3pEwDgpMqzCcK1DeF23O+7w7gHYDHLDfLmPu0uKChr+ESXuLFhHfMB5bwLmL8/9f ZbB/KqPTESHk9LYWYoKlWvv7jigtMTGzui4ocMKCroA1iD8b7WlzyNZWcfTOCvAdVlHe /jKjb8MIAjNKfZjbyo6Xo7rabCANxTxQxQ0/2bRGtlCk169t/gyrMCJ1PUYSRtkQYkgw z97w==
X-Gm-Message-State: AD7BkJJvDQTWW6R4TPONjQZvt3w6hY/nG9hovyiKWEhefK/gJCrASAZhjP0rhGLNX/bdp8xxGFgB4onSXI0nYwxI
MIME-Version: 1.0
X-Received: by 10.37.230.198 with SMTP id d189mr8947732ybh.136.1459911287844; Tue, 05 Apr 2016 19:54:47 -0700 (PDT)
Received: by 10.37.203.85 with HTTP; Tue, 5 Apr 2016 19:54:47 -0700 (PDT)
In-Reply-To: <CABvL1xoMA_fF1sTDXJNw8dRGCposS6a1OXP4nVwuvpsyEBSJuA@mail.gmail.com>
References: <9EDD05BA-A6D3-4F37-8E65-19D573324966@ntt-at.com> <57031F98.3080300@mozilla.com> <CABvL1xogUKmLdJgUtwq+-4qQhzn+2Hsq2JK3G-e5vsZKktXy6g@mail.gmail.com> <B1516DDA-1660-4C63-AD3C-569150849467@mozilla.com> <CABvL1xqwqRuSGyNsFD42v_pLTstQHGLG5oTOT6GiXbEGwnBdNg@mail.gmail.com> <CABp8EuLF72MoS+vSrLF0iPn1mEjaa=MQmGoF_4sOZ5_udmZXug@mail.gmail.com> <CABvL1xoMA_fF1sTDXJNw8dRGCposS6a1OXP4nVwuvpsyEBSJuA@mail.gmail.com>
Date: Tue, 5 Apr 2016 19:54:47 -0700
Message-ID: <CABp8Eu+Z_wRMGz9tgoEou_GEMWMNPv8inqq-wgXv4r3yz5F7cg@mail.gmail.com>
From: Benjamin Bangert <bbangert@mozilla.com>
To: Richard Maher <maherrj@googlemail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/VrMzgYmet1ZV6smyrIEv61veTwY>
Cc: Kit Cambridge <kcambridge@mozilla.com>, jr conlin <jconlin@mozilla.com>, "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Polling to adopt VAPID draft
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 06 Apr 2016 03:09:34 -0000

On Tue, Apr 5, 2016 at 7:45 PM, Richard Maher <maherrj@googlemail.com> wrote:
> Hi Benjamin,
>
>> https://tools.ietf.org/html/draft-ietf-webpush-protocol-04#section-6.4
>
> Now I'm completely lost and more than a tad disappointed.

This mailing list is to discuss the IETF WebPush protocol, while some
push implementations have inspired additions, they are separate from
the spec that browsers are working to implement.

>
>> That is documentation for Google Cloud Messaging,
>
> I know. I, perhaps wrongly, assumed the consumers of GCM (et al) would take
> full advantage of the infrastructure. "Collapsing" is a very useful
> optimization option but surely not the raison d'etre of topics?

For WebPush, thats the primary intention.


> I want to subscribe to /SEVERE/PERTH topics for push messages my weather
> app. The fact that old messages are collapsed is wonderful but if you're
> also going to bombard me with /MILD/TIMBUKTU messages (and so on) then I'm
> not too happy.
>
> I want to subscribe to the BHP stock ticker broadcasts and then maybe add
> FMG but I don't want the ASX 200.
>
> Have I really imagined that GCM cann do that?

GCM can, WebPush cannot. What you're referring to has been proposed as
the WebPush aggregation spec, which can be found here:
https://github.com/martinthomson/webpush-aggregate

Cheers,
Ben

v2.8.7 | Report a Bug | By Email