IETF Logo Mail Archive

Re: [Webpush] Delivery receipt may be sent before AS request delivery

Martin Thomson <martin.thomson@gmail.com> Thu, 09 June 2016 01:06 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 91AE612D8D4 for <webpush@ietfa.amsl.com>; Wed, 8 Jun 2016 18:06:42 -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 ggF9qtu7ICvU for <webpush@ietfa.amsl.com>; Wed, 8 Jun 2016 18:06:40 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 B7C0C12D8CD for <webpush@ietf.org>; Wed, 8 Jun 2016 18:06:40 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id p22so13515717qka.2 for <webpush@ietf.org>; Wed, 08 Jun 2016 18:06:40 -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:content-transfer-encoding; bh=tKicJd22tz2jy9FDJpP5Ce1X1a+sefhpEv+G+HOuDQM=; b=ArjX4/OGULITb2uiEQ53922yo6V37FS/bCXO7Xhh5+nqxZp1aaw3MamIFlG19BdVvI iGjOsur0tq8AzmnBoqt+DnaHeB582Qk3/AbiCmVNv3kQ/Z5XE0jwpHW5siiABe+WDwRH 67uAXNBOheui9nVms3tpBIxn435DbtolK0GXBjfaYVvza0BEdAbzTim20cduqQ2WjIWB LYCzZStS6Len13H73nSxTqmYewVoqQ86p88I/UCP9D0bQCd7SLY5FiEsXBNWRQ87poOW fMkEDOk0S0GAF1UzFMSYdy3aSoklZRBbs/BQLZqeRISwxyExL/CwvmvcPIUPjyRwY0qn ha3Q==
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:content-transfer-encoding; bh=tKicJd22tz2jy9FDJpP5Ce1X1a+sefhpEv+G+HOuDQM=; b=X4rxJXLueuAmTITf9XiXMQNMDMq263uGMSfiybMClvhceljHtpMWXoYlSm6bAujiVB swikVh6AtYKmFsZKD0My+vU2Kmq4kKDglGU6pPHA4yYOf5FhE+mWD129/o8aRYbK3wOx 1Ryln4IeI+ldspWWfEEeE/cqD+hrqM9SIQCOB4smaXz21Y/bAR5VZOWhx1y4kBJW+tck w7Zs8BRybkmNYUYK7CETOV7V6QiHTa4KYB9fuBVlqMo4UGLCJUSGFSqZryFGhBWUTnGe Wdrk0kKpZWznmGAVKXiTiFWnmuBA6QErZXzChME0jPR5HoY+UJffUJhW8TJD5iIiTPNk hq8w==
X-Gm-Message-State: ALyK8tIKgqaCjheAAXIzm/K7uNVJltPzF1/YtRdDuYRY2X3xpu501dDcvnnT8yh9VmyZhf7PWHSqo7jtPEcYSw==
X-Received: by 10.55.138.194 with SMTP id m185mr7902068qkd.48.1465434399294; Wed, 08 Jun 2016 18:06:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.104.110 with HTTP; Wed, 8 Jun 2016 18:06:38 -0700 (PDT)
In-Reply-To: <CAN+BUJrTzyUJBVbfv7ftUfNDkUsiAWu_5bLAw6k+9ZgKcPUS6g@mail.gmail.com>
References: <CAN+BUJrTzyUJBVbfv7ftUfNDkUsiAWu_5bLAw6k+9ZgKcPUS6g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 9 Jun 2016 11:06:38 +1000
Message-ID: <CABkgnnU3cUyo1=6qNPbD3QtPL_qDzqiFHG72zxmENL2fx9mnQw@mail.gmail.com>
To: Idel Pivnitskiy <idel.pivnitskiy@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/UydjWdsG9LGUxlPiI04uQZWXlGM>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Delivery receipt may be sent before AS request delivery
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, 09 Jun 2016 01:06:42 -0000

For context:

> Here may be a problem with push messages with a little value of TTL. Message may be sent to a UA and ack may be received from the UA before the AS will send a HTTP GET request to the receipt subscription resource. PS will retry delivering of receipt, but TTL may expire before this.
>
> To eliminate this problem it would be better to introduce separate resource for an AS: something like /subscribe for a UA, where AS may create a receipt subscription.

We originally had the design you describe, but @brianraymor proposed a
simpler design that accomplishes the same goals, providing that you
recognize that a TTL shorter than the time it takes to poll the
receipt subscription resource can result in losing the receipt.

The only good solution to this general problem is to have a longer TTL.

Even if you fix the "bug" you identified, a short TTL can expire
between the time that the message is delivered to the user agent and
before the acknowledgment can reach the push service.


On 9 June 2016 at 09:07, Idel Pivnitskiy <idel.pivnitskiy@gmail.com> wrote:
> Found out a problem with lost of delivery receipts for push messages with
> little TTL, an issue was created:
>
> https://github.com/webpush-wg/webpush-protocol/issues/115
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy
> GitHub: @idelpivnitskiy
>
> _______________________________________________
> Webpush mailing list
> Webpush@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush
>

v2.8.7 | Report a Bug | By Email