IETF Logo Mail Archive

Re: [Webpush] Polling to adopt VAPID draft

Benjamin Bangert <bbangert@mozilla.com> Wed, 06 April 2016 02:06 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 20B1D12D0CB for <webpush@ietfa.amsl.com>; Tue, 5 Apr 2016 19:06:24 -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 e1XFoS3Y5K1Q for <webpush@ietfa.amsl.com>; Tue, 5 Apr 2016 19:06:20 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 CA69712D151 for <webpush@ietf.org>; Tue, 5 Apr 2016 19:06:20 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id d68so39617740ywe.1 for <webpush@ietf.org>; Tue, 05 Apr 2016 19:06:20 -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:content-transfer-encoding; bh=4WoHWQRuPu3RlmU5xi5t5uwGDx49r/BJfezc75yO7wc=; b=NjpJwCU+c9nGLubmWQgJL/Btuf0Y10AqlIoIGQzgmAvsSmf9sq5YMsWU4oWjMFm5WH GGbhFz3AobGQbeWqbpUZXGOvzccbERd/hb5nkNVqKUY6IwQTlLVQf5Fj7K0P3JY4YHbH xBmGi0VRDyEweM9OGODyFMlu8kBrWoaJ8tSjoWRV7YH/k9wsC9hQgDg9I+4NRG4s2bF5 FHiifnNyd3i14BAHLrj5/aZbmPaZFcTjeKFyoAQZLIO3hMPsB+Jp46f34qmCojiwvvr5 oD2JHR52HYFDK3nhwHO8yeEyefv73Im0+uQL/zIoyDlkD+WgeYQTnnQsO/a94Gk/tKcJ OSPA==
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:content-transfer-encoding; bh=4WoHWQRuPu3RlmU5xi5t5uwGDx49r/BJfezc75yO7wc=; b=OX5jihMuB5zcXn2qa6dolFGOqzelzLPNQ7lCCx+ydoQ0IBlCtE9F81BmiyI3A8ja8a AwJ0mq2+rlg+YMyBYCdlcM4oRSrquh76cl49Aa2s3zQHCXxqfbnAU9SojC3biYCc6ieG gwtMUljrT2Qi1DoWYOfhHJ+MK6UCxlh0rm8P4Tv06y5yeaAgEW2LVxzK/orHfBeGJrgf JAaau1ZyNweMAR0MGBQtH4ry+vRdga0D6Vao7Ql9QglQdx7ZcW4+057rZfoVsRVnmWhs 6DROv4O10hLyAHPJ2SCVX1ioyFnpHgaQrs7/NfXZm/ZJloMzH/pN5CWUBWUUCTbCquB8 fnww==
X-Gm-Message-State: AD7BkJLdRrUeoO5CzwQlDffRLBzCnEkDHPpyZDTO/Y7ED5Hz2p9LV2jcJE5pYO0FVB3AZ/ovwfelbtDfoC/o210y
MIME-Version: 1.0
X-Received: by 10.37.230.198 with SMTP id d189mr8885949ybh.136.1459908379932; Tue, 05 Apr 2016 19:06:19 -0700 (PDT)
Received: by 10.37.203.85 with HTTP; Tue, 5 Apr 2016 19:06:19 -0700 (PDT)
In-Reply-To: <CABvL1xqwqRuSGyNsFD42v_pLTstQHGLG5oTOT6GiXbEGwnBdNg@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>
Date: Tue, 5 Apr 2016 19:06:19 -0700
Message-ID: <CABp8EuLF72MoS+vSrLF0iPn1mEjaa=MQmGoF_4sOZ5_udmZXug@mail.gmail.com>
From: Benjamin Bangert <bbangert@mozilla.com>
To: Richard Maher <maherrj@googlemail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/HLDnyCw6ZZUUQ9MKDrdAfR29BCA>
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:06:24 -0000

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