Re: [Webpush] Receipt subscription follow-up

Brian Raymor <Brian.Raymor@microsoft.com> Wed, 27 April 2016 17:22 UTC

Return-Path: <Brian.Raymor@microsoft.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 010C712DA85 for <webpush@ietfa.amsl.com>; Wed, 27 Apr 2016 10:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 RMUcPGauYxHg for <webpush@ietfa.amsl.com>; Wed, 27 Apr 2016 10:22:21 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0712.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::712]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2F6A12D8E4 for <webpush@ietf.org>; Wed, 27 Apr 2016 10:22:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2HBKirHbuUblKg3R/W63GFJgbJevF4+GEvaK/7+PRMg=; b=TI8tlA0Zk4HR91L6TWkNSfE/j3IBLumcs1qKv/Q4YdIZ+Itjw9FeyShE29O4jTXvgVrRmkbV2MGN1kZiAv+LkKPPz05ZPPo059snHGg/h1pzkC7NZBIKivMvws2FV3A8jocgD0k3psfWjsmRkkbcKrHLSDVkpgKDHvtl4Abubpo=
Received: from CO2PR03MB2407.namprd03.prod.outlook.com (10.166.93.137) by CO2PR03MB2405.namprd03.prod.outlook.com (10.166.93.135) with Microsoft SMTP Server (TLS) id 15.1.477.8; Wed, 27 Apr 2016 17:22:04 +0000
Received: from CO2PR03MB2407.namprd03.prod.outlook.com ([10.166.93.137]) by CO2PR03MB2407.namprd03.prod.outlook.com ([10.166.93.137]) with mapi id 15.01.0477.012; Wed, 27 Apr 2016 17:22:04 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Martin Thomson <martin.thomson@gmail.com>, Costin Manolache <costin@gmail.com>
Thread-Topic: [Webpush] Receipt subscription follow-up
Thread-Index: AQHRn07lqbBQG1UN8Ead0PaEULBvX5+c9xVQgABAMoCAAAKaAIAA0sfA
Date: Wed, 27 Apr 2016 17:22:04 +0000
Message-ID: <CO2PR03MB24079FEC854A49F60C66F81583640@CO2PR03MB2407.namprd03.prod.outlook.com>
References: <CABkgnnXKDZvLWxkhFP0R4jW=ZyFwqiqQREFA5BFKH9i4PQCmyA@mail.gmail.com> <CO2PR03MB24076724ECF95BDBB9B83E0F83640@CO2PR03MB2407.namprd03.prod.outlook.com> <CAP8-Fqk8p1HkbJkB60UoE=jeQPa9CKorgc8kqSF7sUMS3FcAfQ@mail.gmail.com> <CABkgnnU_jnSuUX7TC+qy2SwteU1tW9DEAb0uoHmhOcYNQaYuvw@mail.gmail.com>
In-Reply-To: <CABkgnnU_jnSuUX7TC+qy2SwteU1tW9DEAb0uoHmhOcYNQaYuvw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:d::2c5]
x-ms-office365-filtering-correlation-id: 6793e937-114d-45c1-e57a-08d36ec0740a
x-microsoft-exchange-diagnostics: 1; CO2PR03MB2405; 5:UwWdcHv/uU5rDjVteoT7twGeNhF76Tqyzbq10U5kqtThrIjNDyFqT9U9BkTPa7qPqMybDC31BckEsLYNtl7YdpbDcejnsOaKO0cGQIqER8FSi2dwByhZ28vtWKR17bBFCKIDiq3EPvewonab+nTCvw==; 24:24yWNpslGkz/XziSB9ogRJo6voZavTCidApPhcd3YE7kNMsV2XFdp8NoS+oDtE08Sz69TZfX2Pq39Zfgu4gzjvOI34H3E8xlTcBjntbPL+o=; 7:xDnC0GgjTu0IDu8sSI8mUDhj6gxi06b4qyctuAZmNOQrcMKfo0VMzMU+1Kfq3kq5TBojzcYU1nzcMhKbqYfbDfZGqdyTbRms7E/suHOsA8k+z+d6V6i4YQw6nsnmz1zdIeIjL56suvxI4ahTT/9/da/HtodWMuJKAA0SiwG6gApj0K1UD+ilX/P/WDThTmHpfv9X31LRMSwtXruyxsVR2Q==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO2PR03MB2405;
x-microsoft-antispam-prvs: <CO2PR03MB240593E86BD2DB9B5328A15683640@CO2PR03MB2405.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521072)(61425038)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026)(61426038)(61427038); SRVR:CO2PR03MB2405; BCL:0; PCL:0; RULEID:; SRVR:CO2PR03MB2405;
x-forefront-prvs: 0925081676
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(24454002)(12063002)(106116001)(1096002)(1220700001)(5008740100001)(11100500001)(99286002)(2900100001)(2950100001)(19580395003)(19580405001)(122556002)(86612001)(8990500004)(33656002)(5004730100002)(4326007)(10290500002)(54356999)(5005710100001)(87936001)(50986999)(10090500001)(10400500002)(76176999)(189998001)(76576001)(9686002)(81166005)(2906002)(93886004)(586003)(92566002)(102836003)(6116002)(5001770100001)(74316001)(5003600100002)(5002640100001)(77096005); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR03MB2405; H:CO2PR03MB2407.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Apr 2016 17:22:04.7300 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR03MB2405
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/_NI1qBtSR2JxOyZzdjtZAETouEY>
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: Wed, 27 Apr 2016 17:22:23 -0000

On Tue, Apr 26, 2016 at 9:21 PM Martin Thomson <martin.thomson@gmail.com> wrote:
...
> However, in this case, can we request that the application server
> DELETE (just like the client uses DELETE to acknowledge)?

To clarify, you're proposing that the application server delete the same push message resource that was deleted by the user agent to acknowledge receipt of the message? If so, something like:

If the push service receives the acknowledgement and the application
has requested a delivery receipt, the push service MUST return a 204
(No Content) response to the application server monitoring the
receipt subscription.

To ensure that a receipt is properly delivered to the application
server at least once, the application server MUST acknowledge receipt
of the response by performing a HTTP DELETE on the corresponding 
push message resource.

If the push service does not receive the acknowledgement within a
reasonable amount of time, then the receipt is considered to be not
yet delivered. The push service SHOULD continue to retry delivery of
the receipt until the advertised expiration of the corresponding push
message.