IETF Logo Mail Archive

Re: [Webpush] Prefer: wait=0 for Receiving Push Message Receipts

Brian Raymor <Brian.Raymor@microsoft.com> Sat, 11 June 2016 02:14 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 7CD5F12D59A for <webpush@ietfa.amsl.com>; Fri, 10 Jun 2016 19:14:36 -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 x7cOzXz5hOOY for <webpush@ietfa.amsl.com>; Fri, 10 Jun 2016 19:14:34 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0752.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::752]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C47C12B005 for <webpush@ietf.org>; Fri, 10 Jun 2016 19:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=R1VlMt/2koueUEpwEWC3ToasJ9cMN+1QC2nbtc8h+Sg=; b=ic+1aZII/dCFto+A6xRDceTYbMA/H/yJkEcGVf2N5FdFjySpDNSX8GL/JCC0vN4ZJ1n2ZShHrPQlkWakFnhrTAcsBqB3CZjL36YBqzkb2Vwstu8kkw17mC6q0d3PD8XV3m49Xi/l+B8G67cLCmGGpkuDZX6a9ieQZ9xoGw/2eV0=
Received: from CO2PR03MB2407.namprd03.prod.outlook.com (10.166.93.137) by CO2PR03MB2407.namprd03.prod.outlook.com (10.166.93.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.517.8; Sat, 11 Jun 2016 02:14:16 +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.0517.005; Sat, 11 Jun 2016 02:14:16 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Idel Pivnitskiy <idel.pivnitskiy@gmail.com>, "webpush@ietf.org" <webpush@ietf.org>
Thread-Topic: [Webpush] Prefer: wait=0 for Receiving Push Message Receipts
Thread-Index: AdHCmaXPqP5E+T/6TVO6nqulqOJ2zgAsHEeAAA8jShA=
Date: Sat, 11 Jun 2016 02:14:16 +0000
Message-ID: <CO2PR03MB240722CEAAB47888F215A29083510@CO2PR03MB2407.namprd03.prod.outlook.com>
References: <CO2PR03MB240716255D037CD89F1E9BC6835F0@CO2PR03MB2407.namprd03.prod.outlook.com> <CAN+BUJrBD=kMGJGL-nUbVGv3nM3VJ=sUaaZHk634=8+GY13HFw@mail.gmail.com>
In-Reply-To: <CAN+BUJrBD=kMGJGL-nUbVGv3nM3VJ=sUaaZHk634=8+GY13HFw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Brian.Raymor@microsoft.com;
x-originating-ip: [24.16.23.27]
x-ms-office365-filtering-correlation-id: 56af3cc7-5c43-4f13-e444-08d3919e170a
x-microsoft-exchange-diagnostics: 1; CO2PR03MB2407; 6:hagB8f7MQvOad9QQI64xgBRBCrFXDoH6bfYsiC7ZakJr28OpxCMOadnVatvCKITJ/4RsaP+nZvHoqXrPaVWzk2rikJnG9p5eYFHPEyq1f6Pg9mv3VP9BDSvfFOFnLs79gSH7rB4pP2sQMy1TpCx4vMmZcPJUm5X/h5snB7GU6r4Sn5SCk/vXvd7cSEvhj5hGlSoGFVlIAs0pYfoaALgJtEOinXl1qOcEuFcBxe6D0Qu9D5b6kNWZTXAK04rQOxQl+EmZost0mI3Osh4D5vs3j0KEXvPZrct8FCg03VSMPAA=; 5:BSKNSKP6edD5GsnPVECZE3xNIIHe/W07XCb8lrrwQku9B2rcxH5DiTteGoihDmhdxMfeKMNAAd4ST6Ro8uj0xgf/kEjHJxZ6a3eoW7l+/jNQtPIaqixS0OFkJULyBAarkXDIGUMf0J8YazyVN/WH6w==; 24:RoEhHjVFt2H4TIxYR8foK2068jOPnL7OZ0D8zAFaAcbprvNZvjeeZOeCgahsU6NomrcpUOi8xIy+LX4aTKlgyrIPDeP+2XGJaM8VGPGTgA8=; 7:LNej2ZuTflkERj3hRjkJ6nHTu2rA6ZAfryjPz5EKMpXfXmYmNXlw8n2a3ASKxYcDqrbjOp1SUtKcOacoiI/Y7N1F/DsmWrQCWtQeungW3FB5sweQiuDfQvZpShjJmRXdfZS1NAz7XPYneYTm6YHa5hJRLSPXOyKbXcfuHWqTSrV0Ke66WMKtrEKcnXeLfsxBJhFOBdwSfzI6d4TBwstQR14SqINjIxXs6VgCbGpK0JI=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO2PR03MB2407;
x-microsoft-antispam-prvs: <CO2PR03MB2407E93F34F221D14BC2F41683510@CO2PR03MB2407.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(148322886591682)(166708455590820)(209352067349851)(31418570063057);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(61426038)(61427038); SRVR:CO2PR03MB2407; BCL:0; PCL:0; RULEID:; SRVR:CO2PR03MB2407;
x-forefront-prvs: 0970508454
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(78114003)(189002)(24454002)(377454003)(199003)(12063002)(74316001)(54356999)(101416001)(10090500001)(8990500004)(19580405001)(68736007)(76176999)(122556002)(2906002)(5005710100001)(5002640100001)(10290500002)(19580395003)(50986999)(99286002)(10400500002)(105586002)(15975445007)(5003600100002)(9686002)(77096005)(92566002)(5001770100001)(106356001)(97736004)(8936002)(6116002)(11100500001)(3280700002)(189998001)(86612001)(5008740100001)(87936001)(81166006)(107886002)(81156014)(3660700001)(2950100001)(3846002)(76576001)(2900100001)(8676002)(2501003)(102836003)(66066001)(86362001)(33656002)(15650500001)(5004730100002)(586003); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR03MB2407; H:CO2PR03MB2407.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; CAT:NONE; LANG:en; CAT:NONE;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
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: 11 Jun 2016 02:14:16.5415 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR03MB2407
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/IYN_Cu9RvmssSegXy9Q2ETg27Nw>
Subject: Re: [Webpush] Prefer: wait=0 for Receiving Push Message Receipts
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: Sat, 11 Jun 2016 02:14:36 -0000

I’m not hearing broad support to add this feature during WGLC.

Closed https://github.com/webpush-wg/webpush-protocol/issues/113


From: Webpush [mailto:webpush-bounces@ietf.org] On Behalf Of Idel Pivnitskiy
Sent: Friday, June 10, 2016 11:59 AM
To: webpush@ietf.org
Subject: Re: [Webpush] Prefer: wait=0 for Receiving Push Message Receipts

Thanks Brian,

Yes, as a design of receiving push messages and push message receipt is the similar and they are both use server pushes, will not be a problem to reuse already implemented code base to allow this feature for an AS too.

Advantages:
• More flexible logic for AS (it could choose how it will request receipts);
• Possibility to reduce number of always opened connections to the PS, because if a UA may be unavailable most of the time we can not say the same about an AS. It's online most of the time, but can request push message delivery rarely.
Previously Kit also considered to add this feature:

https://github.com/webpush-wg/webpush-protocol/issues/18#issuecomment-97478621


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

On Fri, Jun 10, 2016 at 1:19 AM, Brian Raymor <mailto:Brian.Raymor@microsoft.com> wrote:

https://github.com/webpush-wg/webpush-protocol/issues/113

Idel has suggested the addition of the Prefer: wait=0 option to section 6.3. Receiving Push Message Receipts to allow application servers
to have the same option for immediately checking/receiving receipts as user agents have for immediately checking/receiving messages.

I'd appreciate broader review and comments about whether this is a useful feature.

The addition to 6.3. Receiving Push Message Receipts would be:


An application server can also request the contents of the receipt subscription resource immediately by including a Prefer header field [RFC7240]
with a "wait" preference set to "0". In response to this request, the push service MUST generate a server push for all receipts that have not yet been delivered.

A 204 (No Content) status code with no associated server pushes indicates that no new receipts are presently available.




_______________________________________________
Webpush mailing list
mailto:Webpush@ietf.org
https://www.ietf.org/mailman/listinfo/webpush

v2.8.7 | Report a Bug | By Email