IETF Logo Mail Archive

Re: [Webpush] Polling to adopt VAPID draft

Richard Maher <maherrj@googlemail.com> Wed, 06 April 2016 02:45 UTC

Return-Path: <maherrj@googlemail.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 ACC7F12D51F for <webpush@ietfa.amsl.com>; Tue, 5 Apr 2016 19:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, 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=googlemail.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 O9-lFol6UiAY for <webpush@ietfa.amsl.com>; Tue, 5 Apr 2016 19:45:35 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 F416212D0A7 for <webpush@ietf.org>; Tue, 5 Apr 2016 19:45:34 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id c126so23970996lfb.2 for <webpush@ietf.org>; Tue, 05 Apr 2016 19:45:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=2yNWCymV2NjtSO2DQXS1JoGG7fCbSsp7W6tKElEw2/w=; b=zRNdcEohsLX+ETsKhDQ/abkDKDlb26GRqPBl26DZwwaxzfPpMcQFyzgP9nB3yDF6cD oh+gI5CBVLnTIWmbFX3h/rwPHrTmwJD2R8+NsHGTm2S66OLKHTGtygx4HDL6WHc/1uK2 fbCDHYu0NXH8d1LVXCm5kQWmfcdCHNyjZEga933Urt+4mup9J+pGr0Qw43c/U/an3ZgE YvbrCgCMQcx6iAG8FTdO+3HEkSGNBZJU4XckhKxSP7Mgn+fb8OeFZQr8ETT1dPb2DDoF BI0HAv75iY900oDqMsHsoSZ0lmQR0IcLJnYjwjBGhEVf50aYNJHxXRtymoGCkHXwR2pa utPQ==
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=2yNWCymV2NjtSO2DQXS1JoGG7fCbSsp7W6tKElEw2/w=; b=Sfn9qS4oBq7ysKz/mK2V+d3+hHLzdZ6wZ/5P+kqHsXSJ71yhNeBPq40ypyLL8cppwm O1fNBsb4oi4Vi2qVOVe7OZtS5D1i3QznHi/ymm5aP1TmTVjlqlbWbg2GlfGJR8N2xq1H 2GCILLxi8RZYyUJXNxFZ0JkKqXcz5lDpvs0VzatCiRa86EyXtUb+0t2nz/l0f/cHamBs bPElynUG7UVCfD2mKZFYalvzGNDmvG24s4WjB4OTptyNELjzWZAQfwbNFFnlUqNW1rZd bdqhQhSJbszrknn7hrj2bfJg8k78DW0Hr7KYEclOvpOcJxrQhlKWoqmdWO24gbNGOsdF gv/Q==
X-Gm-Message-State: AD7BkJKE1/zUTEjQ3WK/YtKHr/3+wcj3g3L5OxklL3/LD6R1v4nD7hO+qUJLfZAZtkfzXV7wcjgXcxtkRqIk2Q==
MIME-Version: 1.0
X-Received: by 10.25.21.231 with SMTP id 100mr12418819lfv.146.1459910733142; Tue, 05 Apr 2016 19:45:33 -0700 (PDT)
Received: by 10.114.200.208 with HTTP; Tue, 5 Apr 2016 19:45:33 -0700 (PDT)
In-Reply-To: <CABp8EuLF72MoS+vSrLF0iPn1mEjaa=MQmGoF_4sOZ5_udmZXug@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>
Date: Wed, 6 Apr 2016 10:45:33 +0800
Message-ID: <CABvL1xoMA_fF1sTDXJNw8dRGCposS6a1OXP4nVwuvpsyEBSJuA@mail.gmail.com>
From: Richard Maher <maherrj@googlemail.com>
To: Benjamin Bangert <bbangert@mozilla.com>
Content-Type: multipart/alternative; boundary=001a113f1866a721cf052fc7f4be
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/q41rA9zyhHGzg5Q9neN40DR8uQA>
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 02:45:37 -0000

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.

> 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?

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?

Cheers Richard

On Wed, Apr 6, 2016 at 10:06 AM, Benjamin Bangert <bbangert@mozilla.com>
wrote:

> On Tue, Apr 5, 2016 at 5:33 PM, Richard Maher <maherrj@googlemail.com>
> wrote:
> > Hi Kit,
> >
> >
> >
> >> I don't follow this point. What do you mean by "a server subscribing a
> >> client to a TOPIC”?
> >
> >
> >
> > I may have misunderstood the documentation but WRT
> >
> https://developers.google.com/cloud-messaging/topic-messaging#managing_topic_subscriptions_from_the_server
> > and
> >
> https://developers.google.com/instance-id/reference/server#create_a_relation_mapping_for_an_app_instance
> > , in the absence of any client topic-subscription mechanism what else
> can we
> > do?
>
> That is documentation for Google Cloud Messaging, not WebPush. Under
> WebPush, topic collapsing is purely an appserver option when sending a
> message such that if a message of the same topic was already stored,
> the new message will replace it.
>
> As far as I know, there are no implementations of Webpush topics yet,
> the spec describes it here:
> https://tools.ietf.org/html/draft-ietf-webpush-protocol-04#section-6.4
>
> We're probably a few weeks or month or so out from implementing this
> for Firefox.
>
> Cheers,
> Ben
>

v2.8.7 | Report a Bug | By Email