Re: [Webpush] Receipt subscription follow-up

Martin Thomson <martin.thomson@gmail.com> Tue, 26 April 2016 05:26 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 6744312D097 for <webpush@ietfa.amsl.com>; Mon, 25 Apr 2016 22:26:27 -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 RjLRi_VKZDvI for <webpush@ietfa.amsl.com>; Mon, 25 Apr 2016 22:26:26 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 3927212B017 for <webpush@ietf.org>; Mon, 25 Apr 2016 22:26:26 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id d62so6103173iof.2 for <webpush@ietf.org>; Mon, 25 Apr 2016 22:26:26 -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=uuzBMf7/4jfNYQ8wISdNvsPsKlMpdn0CPmPkCp3xG54=; b=FdMtq4YnglRtA8dqXJSn9u5IhWCo3I2C9yx/XLOR7W1yWBoOrc75W3Gp8fvdRpGQjN X8zHEYyyudLbjAk019eTqGgPhiaYBoYEhO43O4ju8CfrawdyeglhgCJhu2z5KTSoCKV0 acG9O/zLAreV1lf+aT7B2Kj64JzAJ0ABa/SAZHTcVUuqWZ+DcZsAfeqrAF1l1Jr8cRms 8x6kLzNR3WrVNgQiHf1joSREz3bbjhGNSuWJh2jJurVVPtzEpNpY3A/ePR9ODkH/LZjr M/pyg5Ky0iD7RJknIY4uhBiF4Cg9DHHTjYC82K0R11+Wvm2QQEeG8V9lIS59tp4giquR fY5A==
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=uuzBMf7/4jfNYQ8wISdNvsPsKlMpdn0CPmPkCp3xG54=; b=cned7DMXMDut0uAIOAe9uFQZTDR24XDHtCAKUcPgm808P9uGCWS7VqpAnrE7aFXTD2 523Zr8qOHGGBeryOB5C20s8KFqH2BXQec77BZMPMEh2YBunVRJumbZgjVMVlxTiv4iN+ 4uyc81wLFZ+r2cXv1mhIxKg+Ck1TnVA2KmPdAUTPRfaNG4xVNkmIN05gOvOWBKKv5lZw K/QAgsslI2ZlzYgi+L/HEAJI4TWcrLSDMuVEnrincjDUoQyr9kQdYeoYYZtTLXtjtMZR 1LhNH7vpmB2YtLktZY0RNUIN9zZDvHhcfltqN9wDw9TMQimcpjAfFe1SYf6Sxl68prGO oYDg==
X-Gm-Message-State: AOPr4FW4l33ZwTihUfXq++OflqyE6z4UbhZxWtP+Rbkn3SnN62gdCI+7CUK+QRsfMwTg2Mp3gxwWfT8QxbFWug==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr1275873ioe.190.1461648385681; Mon, 25 Apr 2016 22:26:25 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 25 Apr 2016 22:26:25 -0700 (PDT)
In-Reply-To: <CAP8-Fqnd4uwcSkfTFuNqpLH0dXABJ_jTTLTd2YtwFG30bYZHaw@mail.gmail.com>
References: <CABkgnnXKDZvLWxkhFP0R4jW=ZyFwqiqQREFA5BFKH9i4PQCmyA@mail.gmail.com> <CAP8-Fq=Oi_kGebcRsyHYQdXWwLxFQxFwR=jeOyKS-+vW7eE=0w@mail.gmail.com> <CABkgnnX35n3K=cGTC2EvwG3=w6X7uWCikw+QFqhO7-RiLV8zJQ@mail.gmail.com> <CAP8-FqmcguLQaVxeNs1ROAG0XEBgYNtDiJ3+sYUcxmRrFfou1Q@mail.gmail.com> <CAP8-Fqnd4uwcSkfTFuNqpLH0dXABJ_jTTLTd2YtwFG30bYZHaw@mail.gmail.com>
Date: Tue, 26 Apr 2016 15:26:25 +1000
Message-ID: <CABkgnnUeStc02ePuT_hu2cfeqmAKWtqvF85yZpdFx+vj7JLL2Q@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/PVkDNk8u1cI2TP37P4i6jqJ5HZc>
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:26:27 -0000

On 26 April 2016 at 15:22, Costin Manolache <costin@gmail.com> wrote:
> So a PS requiring VAPID can just return the same URL, based on VAPID.

That's not a rule we have.  I'm in two minds about whether we should
write it in.  If we want to have this happen, we should definitely say
that it's possible though.

I was imagining a case where you have VAPID tokens issued on a more
granular level than you have receipts being routed.  Imagine you have
one receipt subscription per region, but a single centralized
controller of the VAPID key so that all the different regions can be
counted by the PS as a single entity.  In that case, inferring from
VAPID might cause the application server some issues.