IETF Logo Mail Archive

Re: [Webpush] Require the TTL header

Brian Raymor <Brian.Raymor@microsoft.com> Fri, 05 February 2016 05:42 UTC

Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F1FB1B35A4 for <webpush@ietfa.amsl.com>; Thu, 4 Feb 2016 21:42:22 -0800 (PST)
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
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 r-ncnWlbQIvD for <webpush@ietfa.amsl.com>; Thu, 4 Feb 2016 21:42:21 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0109.outbound.protection.outlook.com [207.46.100.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A64A1B35A3 for <webpush@ietf.org>; Thu, 4 Feb 2016 21:42:20 -0800 (PST)
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=WlZRF5F/+b5FLg84ltOq8lLnUzbha8d2jyHYukCwDwE=; b=hxZ7eyyzYys5MpOd/ddhoBc2mvV1PFX4RuvhTPY/skux6FTsVh/hApRWU8l3lLZ51vlWQMUf1vNnLbpJtqULiHhTyxk4bIsOj08kYn+WtckJ4k7wcy6WaVZ6KOw2zoFVNxPB3k3uGsR2KtL4oGgCy4Ohe+/sh7OCceHD+U6yu9I=
Received: from BY2PR0301MB0647.namprd03.prod.outlook.com (10.160.63.14) by BY2PR0301MB0645.namprd03.prod.outlook.com (10.160.63.13) with Microsoft SMTP Server (TLS) id 15.1.396.15; Fri, 5 Feb 2016 05:42:19 +0000
Received: from BY2PR0301MB0647.namprd03.prod.outlook.com ([10.160.63.14]) by BY2PR0301MB0647.namprd03.prod.outlook.com ([10.160.63.14]) with mapi id 15.01.0403.016; Fri, 5 Feb 2016 05:42:19 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Benjamin Bangert <bbangert@mozilla.com>, "webpush@ietf.org" <webpush@ietf.org>
Thread-Topic: [Webpush] Require the TTL header
Thread-Index: AQHRX7qxmPHR5E4P70WaFLGI8LoOcp8c4q4A
Date: Fri, 5 Feb 2016 05:42:19 +0000
Message-ID: <BY2PR0301MB06477C93FA8937F0ABD4393383D20@BY2PR0301MB0647.namprd03.prod.outlook.com>
References: <CABp8Eu+oBj8XKWbqd9ypT_mQWzMxXDe+cBR_vqk=rJ=6tM3tFA@mail.gmail.com>
In-Reply-To: <CABp8Eu+oBj8XKWbqd9ypT_mQWzMxXDe+cBR_vqk=rJ=6tM3tFA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: mozilla.com; dkim=none (message not signed) header.d=none;mozilla.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2601:600:8000:5a8:a991:fd36:d5f3:19e]
x-ms-office365-filtering-correlation-id: 8375cac5-27ac-4bf4-ca81-08d32def1cf3
x-microsoft-exchange-diagnostics: 1; BY2PR0301MB0645; 5:kQeXz1/Y2QSreQ2KKhlPmAZEDWng29Ku4FpezCinC0wN5PIyikZQCw0NJCSUwdG+0qYqSSaewCkl6R4Sd6u4r5/5ZxW5NL4ds7v0SgNw87lSBnQaL9NmlclrO5H6wKwoXFXAAJDvWMbHNvE/NTblKQ==; 24:+3oBBC3awmexZg2IiVlAEMzeFBqiORdOBiyQCabtvq7W7qNnmMbtu5fnfUWHF+yC5YhQ+eelG5vN+jP7vBhhS/VXfBu0VC2rolWyVZ9MjDk=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0301MB0645;
x-microsoft-antispam-prvs: <BY2PR0301MB0645E44828C6F1E3AB38173B83D20@BY2PR0301MB0645.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(61426038)(61427038); SRVR:BY2PR0301MB0645; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0301MB0645;
x-forefront-prvs: 0843C17679
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(76576001)(77096005)(40100003)(87936001)(10400500002)(5004730100002)(5005710100001)(33656002)(11100500001)(10290500002)(5003600100002)(5002640100001)(10090500001)(74316001)(189998001)(2900100001)(3280700002)(5001960100002)(5008740100001)(3660700001)(586003)(1220700001)(102836003)(1096002)(76176999)(122556002)(92566002)(6116002)(15975445007)(107886002)(106116001)(50986999)(19580395003)(54356999)(2906002)(2950100001)(86362001)(2501003)(5001770100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0301MB0645; H:BY2PR0301MB0647.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: 05 Feb 2016 05:42:19.2575 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0301MB0645
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/wwCyRhgQ3DbSdkQszvgbAXUG8rU>
Subject: Re: [Webpush] Require the TTL header
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 05 Feb 2016 05:42:22 -0000

> Can we require a TTL value for web-push notifications?

I'd support this requirement if it helps to enforce correct behavior in implementations.

> Regarding the resource creation, the spec does not clearly state whether a Location header should be returned for a TTL of 0
> since its intended that the message is only delivered to an online user. If so, it would be useful to mention.

RFC7231 states:

http://tools.ietf.org/html/rfc7231#section-4.3.3

   If one or more resources has been created on the origin server as a
   result of successfully processing a POST request, the origin server
   SHOULD send a 201 (Created) response containing a Location header
   field that provides an identifier for the primary resource created
   (Section 7.1.2) and a representation that describes the status of the
   request while referring to the new resource(s).

> If it was a required header, we could return a 401 which would very quickly alert developers about the problem.

Did you intend a 400 (Bad Request) rather than a 401 (Unauthorized)?

...Brian

v2.8.7 | Report a Bug | By Email