Re: [Webpush] Receipt subscription follow-up

[Costin Manolache <[e-mail]>]

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.

Even if a PS doesn't require VAPID - it can still use a derivative of the
public key
in the receipt URL.

Costin



On Mon, Apr 25, 2016 at 5:02 PM Martin Thomson <[e-mail]>
wrote:

> Not wanting to steal, Brian's thunder here, but this is the change we
> discussed during the meeting:
>
>   https://github.com/webpush-wg/webpush-protocol/pull/84
>
> It's good stuff, but there's a small wrinkle I thought that I'd raise:
> https://github.com/webpush-wg/webpush-protocol/issues/85
>
> In short, Brian's proposed changes to receipts are good, but we need
> to be clear about how an application server might choose to send a
> receipt subscription obtained from one push in subsequent pushes.
>
> I propose using origin (scheme+host+port).  If they are the same, then
> a receipt subscription obtained from one push can be used with any
> other push to the same origin.  The server is required to understand
> these subscriptions (or not raise any errors if it can't).
>
> _______________________________________________
> Webpush mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/webpush
>