IETF Logo Mail Archive

Re: [Webpush] Proposal: different push message resource URIs for AS and UA

Idel Pivnitskiy <idel.pivnitskiy@gmail.com> Thu, 02 June 2016 12:13 UTC

Return-Path: <idel.pivnitskiy@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 96A9C12D6C7 for <webpush@ietfa.amsl.com>; Thu, 2 Jun 2016 05:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 PyFF-G1jieMi for <webpush@ietfa.amsl.com>; Thu, 2 Jun 2016 05:13:42 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 B04FD12D6C3 for <webpush@ietf.org>; Thu, 2 Jun 2016 05:13:42 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id z123so49439038itg.0 for <webpush@ietf.org>; Thu, 02 Jun 2016 05:13:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PoeRB3PeHBaVeU6aSUVy5sMuz1RtYWuXAa5gIZGOs2s=; b=RiN6QDQgPZdt8tHDXKL6rd7uQgZjZ/o/hF+EsyPm1aKMmp1AAsnh9n9bB2GhdA6B6m FT22XkLkwG8P/zN6k3sapGciwdA8H9WTMk2qllqS0dp+NMs2tjM+mEtRsG+AtPc8qEnM /NkCZ7Z23JxfuGhE1ViuVacpX4cGemajuE7aUtK+5Z0PdPCSUJJOwJtz037bth0nNMg2 Q57RWlzoSwzE4b4DYX7AJlPNQvOjw0NAM9QYr69SnDBj9fyPyIbTK/WZL+4/Fq69/psF tAOOPXBc7/DG76kJ8t8YUQczI972JrtMaebCedhXRfpQAf81NBUv7qYJDAaiUBAAobSQ mbXA==
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:from:date :message-id:subject:to:cc; bh=PoeRB3PeHBaVeU6aSUVy5sMuz1RtYWuXAa5gIZGOs2s=; b=CMuajsqJHKrFmUP9eHjkvNrLJYUBeuo0lnDJQbzPQmJJeRSjUkKzTikOdRDmQmwRdj q3C6liOmzdg7avs6vb/I2wGTBz0vdkRnX314kLl09BG8w+Za2/2QQl/59+RNWMtEAAgS c7r08uqL4yg5TxpIH4KSWxVlaRIwugSOeH5HPK8jKxBB6uotff7+lF7RoB1GXNy5OLGq DwWty6iCn6n1gf86BdyC4foqyxC3QSUwe03V54zD2c1amWl7v+S07FW3UuJSV4hEqrbh KOOYZQduhXeR+0qdXIuIYCOywMT8ZYHsXPvnfZSM6rA6+vDD5udC0QBCVRrcvAe7mCOD f8yw==
X-Gm-Message-State: ALyK8tKnN5hWx6Hbl/vfWvWYARwvVHyH0vta9RvFEDBpsBYNxlIBsNlkRHILlqRNXuHEDiIZKsG36ZumYAkKfg==
X-Received: by 10.36.94.68 with SMTP id h65mr3173822itb.45.1464869622035; Thu, 02 Jun 2016 05:13:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.43.197 with HTTP; Thu, 2 Jun 2016 05:13:02 -0700 (PDT)
In-Reply-To: <CABkgnnVGXivVLZFoFT7sxh4T1oMrNZOBL+nGD7TNnZWL8t6H6Q@mail.gmail.com>
References: <CAN+BUJp8CK-wBHqCf9sen042eJ4PA0JmoLoT07oqr755q6aZRg@mail.gmail.com> <CABkgnnVGXivVLZFoFT7sxh4T1oMrNZOBL+nGD7TNnZWL8t6H6Q@mail.gmail.com>
From: Idel Pivnitskiy <idel.pivnitskiy@gmail.com>
Date: Thu, 2 Jun 2016 15:13:02 +0300
Message-ID: <CAN+BUJoWSx5EFGRLLD6rxDJHSjs3LY_vA3xDkSYThfLrWwYX3Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a11448a9676bf3c05344a8953
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/Ct4kG_AxHhuKnnbed8PrqBXfzAQ>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Proposal: different push message resource URIs for AS and UA
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: Thu, 02 Jun 2016 12:13:44 -0000

>
>  If the AS wants to abandon a push message, this gives it a way.
>

It's not clear in the draft. Also here is no clarification about how acks
should be implemented. Some implementations, for example, might ignore (or
respond with a error) DELETE /d/... requests for push messages which aren't
sent to the UA yet. Looks like a hack and will not work with each
implementation.

The other feature that a single URI provides is the fact that UA and
> AS can agree about the identity of a push message if that is ever
> needed.  (We don't expose this in the push API, so it's not useful in
> that context, of course.)


In most cases receiving receipt is enough for AS. I can't imagine situation
when I need identity exact push message, if AS has already received
delivery receipt. In any case, identification of push messages requires
additional communications between UA and AS, which increase power
consumption. It a little bit mismatches with the goal of the draft.
But ok, if we want to keep this feature, we may describe that the first (or
last) n symbols of a push message resource should be identical for AS and
UA. But the whole URI must be different. Just to prevent unexpected
behaviour and completely delineate the opportunities of AS and UA.

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Thu, Jun 2, 2016 at 5:11 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 2 June 2016 at 05:51, Idel Pivnitskiy <idel.pivnitskiy@gmail.com>
> wrote:
> > It gets ability for an AS to send DELETE request to this URI.
> Consequently,
> > it may cause acknowledgement for a PS and sending a push message delivery
> > receipt to the AS.
>
> I think that this is a feature, not a bug.  If the AS wants to abandon
> a push message, this gives it a way.
>
> The other feature that a single URI provides is the fact that UA and
> AS can agree about the identity of a push message if that is ever
> needed.  (We don't expose this in the push API, so it's not useful in
> that context, of course.)
>

v2.8.7 | Report a Bug | By Email