[Webpush] When UA should send an acknowledgement?

Idel Pivnitskiy <idel.pivnitskiy@gmail.com> Mon, 06 June 2016 23:03 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 3224412D661 for <webpush@ietfa.amsl.com>; Mon, 6 Jun 2016 16:03:25 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 VtHhOd_daHug for <webpush@ietfa.amsl.com>; Mon, 6 Jun 2016 16:03:24 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 CBEB612D567 for <webpush@ietf.org>; Mon, 6 Jun 2016 16:03:23 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id f67so57412384ith.1 for <webpush@ietf.org>; Mon, 06 Jun 2016 16:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=I82HGYfkNIbDrbFJC61kswIvhtJ4/uvGsqlf8r9mREI=; b=G8iRBV2E9h90H5gpkYaFY3No/uRCZntPMAXGC7AyWogkx38g5REKXBsg1plISvLsDV C6X0colsfs1CgMcl0TOguZ+UA00sjYTzt0+Ym+h9o4/Gk3L4R0VXKicZyjFEawa2yySF e5NUfDs3ahdwvjK0v0hyiQLCEppite2bQnsCHky17ytGf8TTg7WbDIQi/mYU5ckIqjrl yjRcttw5A7LVr3kVqzgWnZ03Y+EreRNrPH4NOgWqouJ4f28E/AKpfaQgeCQRH5/nbW8u YvTpW6YyMlTM4+6z/p8hj2YBlPtmBNC4LdaHW3gVkul0exyv8Ea67RqYn9O9DvI4bqAR WkvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=I82HGYfkNIbDrbFJC61kswIvhtJ4/uvGsqlf8r9mREI=; b=MCLOq1yosFaOeyozr+p3g3boFq7rt64o1F9AGynaH7zPIM6otJG8wDV6EBxpahS4FF JF5+cpam9J84DqX4xq6zqfLzBoawinhiaSe5LiqBA4Rkz8iu3dTYgaHg2TWZ9B1FOUoH fmTQMxayLS/0iEsb7M6KA0EjKlcz8+FLC1bkr4EKZ6AZH8IF9/poq/tHV+4agIjfnb2Y jXmNlB5yaBvZQt8YJROvB2W/qkY0O23wDGs7IjSx40RNE5DOr4TK2bMXtcDHhySbY50V Y0s7UUs7A8MqzkF0bRhfHUa+GtmtztHHQylgkNJDtTeO2K2xfRL2bjgoS1d+h1X5D8zP QIow==
X-Gm-Message-State: ALyK8tI9sStlJQHBghnOgQVdQ3wP0r8RHbDlqMPLvVbQyMAJbEHefklU97v+k+OQOTNorcFWsOgtZ0LM63uhkw==
X-Received: by 10.107.148.143 with SMTP id w137mr25225728iod.63.1465254200508; Mon, 06 Jun 2016 16:03:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.152.131 with HTTP; Mon, 6 Jun 2016 16:02:40 -0700 (PDT)
From: Idel Pivnitskiy <idel.pivnitskiy@gmail.com>
Date: Tue, 7 Jun 2016 02:02:40 +0300
Message-ID: <CAN+BUJpdSB-HvT6VQzVcAPqzwb_pn=HzLOC3r4ntSKjDh3ffLA@mail.gmail.com>
To: webpush@ietf.org
Content-Type: multipart/alternative; boundary=001a113fd48629ea550534a414a6
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/_p-hFsMwf4ly8rPCqLR8dmK86DI>
Subject: [Webpush] When UA should send an acknowledgement?
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: Mon, 06 Jun 2016 23:03:25 -0000

Just a question: When should UA send an acknowledgement? Immediately after
receiving a push message or after decryption/decoding/processing a push
message?

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