IETF Logo Mail Archive

Re: [Webpush] Receipt subscription follow-up

Martin Thomson <martin.thomson@gmail.com> Tue, 26 April 2016 05:03 UTC

Return-Path: <martin.thomson@gmail.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 3C2AD12D09D for <webpush@ietfa.amsl.com>; Mon, 25 Apr 2016 22:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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=gmail.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 q0hzfkcCcFK1 for <webpush@ietfa.amsl.com>; Mon, 25 Apr 2016 22:03:51 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001: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 9AD8D12B03D for <webpush@ietf.org>; Mon, 25 Apr 2016 22:03:51 -0700 (PDT)
Received: by mail-ig0-x22b.google.com with SMTP id bi2so86800136igb.0 for <webpush@ietf.org>; Mon, 25 Apr 2016 22:03:51 -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; bh=kqYHAB3Z7UkQPePRLWLxCl+qDFPyjm5p/jJdNCB2LjE=; b=nrPzpaPG+woyMv0l4Q/FDQPFl5r6ElmIo0qtUBqIaDYljGpJlskfIVELW6LBa5OeVN T/akTHxmHUDetF4jHlze9t6SOqlSFmaxNChW0L7zYB5Dcy68jZ+lZuwPhl8+gyAE5rQE nZ4Pj2XYiAjSZPSWBH0TSQvV106/jRO7LcqKS154H70dMPqAEXf41GV7Y83tgL3f5ZS8 k1COQFkk4wv1WqKK+uvLFBbRRLey+KLxor0VucFNa+32EFMVneTiq2DA52mtY9b/QJeq cpKO/uPP0v59MxsGG+zXf9XcTY9LbSJaHBM/jjjDC7fm4+Hs5hPx2M15uhsE+VX9mKDg LCFw==
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=kqYHAB3Z7UkQPePRLWLxCl+qDFPyjm5p/jJdNCB2LjE=; b=N2o0VixT3xex1ge3pI1GyNRlbDO5NKLPV91Q3OVVqIkR5JZeIUEjsOrCiERLdl4lQz n5YnjqQbUT2r8/gTtzvfDAARLIkrpDfeYbyXcjDC+QKJyyeS0cGptraCj2Y44BqJLtxM VNw4WBZzdEG27ThK35mb11kHCyw7WtddSTM5FjQ+vrNq+0gWZMdDzt+HJW5kmlv4bDhh /NrwydiW32JKJ6SL44rw/dVwq5/n7aeqSl7a/uD+WV8EmtvQFCBp32DCJ0MaY1x8FUBY wxrJEVIDIHH7g3YSfM0eOkA3OpFRnEsTESK1sZfLdGXNgOetvMdJn0Tk9y9Pvyi07x8W NS4g==
X-Gm-Message-State: AOPr4FXevjRiPo0R3OjZjSHnq00S/nPg03In12poutH8P7ydcmDkv7IPC9SHfVIXkROWhNxYn2ZMoDEangN41A==
MIME-Version: 1.0
X-Received: by 10.50.111.15 with SMTP id ie15mr1189732igb.94.1461647031062; Mon, 25 Apr 2016 22:03:51 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 25 Apr 2016 22:03:51 -0700 (PDT)
In-Reply-To: <CAP8-Fq=Oi_kGebcRsyHYQdXWwLxFQxFwR=jeOyKS-+vW7eE=0w@mail.gmail.com>
References: <CABkgnnXKDZvLWxkhFP0R4jW=ZyFwqiqQREFA5BFKH9i4PQCmyA@mail.gmail.com> <CAP8-Fq=Oi_kGebcRsyHYQdXWwLxFQxFwR=jeOyKS-+vW7eE=0w@mail.gmail.com>
Date: Tue, 26 Apr 2016 15:03:51 +1000
Message-ID: <CABkgnnX35n3K=cGTC2EvwG3=w6X7uWCikw+QFqhO7-RiLV8zJQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Costin Manolache <costin@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/8VU2BxeRbVwfcuasUd1pakPnvqM>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Receipt subscription follow-up
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: Tue, 26 Apr 2016 05:03:53 -0000

On 26 April 2016 at 14:47, Costin Manolache <costin@gmail.com> wrote:
> Seems reasonable - but it should be optional if an App Server is using
> VAPID,
> since the push service can simply use the VAPID public key, and it
> simplifies the
> AS logic.

I was talking primarily about what the application server has to do to
decide what to send.

If this were solely rate limiting, I'd agree.  The choice to send 429
can definitely use the token.  The problem is if there are multiple
application server instances and the push service decides to send the
same subscription back to two different instances, then things might
break.  The inclusion of the receipt subscription in the request is
permission to merge receipts.  The push service shouldn't merge
receipt subscriptions without permission.

v2.8.7 | Report a Bug | By Email