IETF Logo Mail Archive

Re: [Webpush] Require the TTL header

Costin Manolache <costin@gmail.com> Wed, 17 February 2016 19:38 UTC

Return-Path: <costin@gmail.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 8D8961A0AFE for <webpush@ietfa.amsl.com>; Wed, 17 Feb 2016 11:38:17 -0800 (PST)
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, 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 cgCFnc1D2PPY for <webpush@ietfa.amsl.com>; Wed, 17 Feb 2016 11:38:15 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (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 ACD361A0378 for <webpush@ietf.org>; Wed, 17 Feb 2016 11:38:15 -0800 (PST)
Received: by mail-ob0-x22d.google.com with SMTP id jq7so30794269obb.0 for <webpush@ietf.org>; Wed, 17 Feb 2016 11:38:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hvc7pZDGKi3g9hWxMdviCU9fsr3gu3+5VUfwqeL2i3k=; b=MJ7bJmGnp3dIRRFayI2bimU/Izb5bOk7AUi6GIGlHqzTH7eguGHHhye91Bqaxt1z3J jEepZw+OgqJViMdvUoOwQ8T8D/Gvnd98xJUzMAuY0ak0YKjm9DbCFk0p8HsfpJtUQP21 tdqePuqyXET74I7PtVWe5y0AJgtvhx/vdDVMcc8iMpJ/DaF0yQwX4c3hoHETSrskeGWq E7YnkArpXZUl6AivfHJQYZnhcUMx+oPaCGp5jKI2J0UUAQdEoyOAI+70DpNHOCMABbjS 3NJHxW6vSUzYESAxZnX/rHvYaQZ/Y0xBg5lNIP8Ck6pHn+mSm3pRelNzLrrMgxadno1q 8UJg==
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:date :message-id:subject:from:to:cc:content-type; bh=hvc7pZDGKi3g9hWxMdviCU9fsr3gu3+5VUfwqeL2i3k=; b=LeeH86QHtvKcsExkZ86FWpJt68hrJKDVvKm9OUMFMhnTyqgvvEoSMnFhpTcXUWVnzB her17YY38BMhg+Iuf5Y/UJ+e4U73dBr/i6KMale9GwsLpjpEk6c7f8YBLq4ImUyx1M2W ZKfHC88voSs/2Wul2WE2KWV2+beMgHVTCQlGQIoqBfaGEfTXGlNGPM06xZQ01E7cqxSI aW66v2/ZMQMuGou7tSuV2C/yvrACRhHanKuDIk9eGdKVecnRncNd8ZiAIPYvGTIXhN+E 9SQ0OmPdMe4xq0CwvOnvxt//5k5uZRELmtxj1bLL5ZaRFG+BpgtBC7epo1ghNkkU9ze6 RMCw==
X-Gm-Message-State: AG10YOQY2PhsXx7q65vWERHjq5ypSTP4OwwIgddWqZ5tdO2HM+Q1DOObNuaeeCyWnwNfwtSftpAEDSsV8dm63Q==
MIME-Version: 1.0
X-Received: by 10.202.102.69 with SMTP id a66mr2600090oic.93.1455737895193; Wed, 17 Feb 2016 11:38:15 -0800 (PST)
Received: by 10.76.68.196 with HTTP; Wed, 17 Feb 2016 11:38:15 -0800 (PST)
In-Reply-To: <BY2PR0301MB06471E5A3BE1442A4EAE0DF683AD0@BY2PR0301MB0647.namprd03.prod.outlook.com>
References: <BY2PR0301MB06471E5A3BE1442A4EAE0DF683AD0@BY2PR0301MB0647.namprd03.prod.outlook.com>
Date: Wed, 17 Feb 2016 11:38:15 -0800
Message-ID: <CAP8-Fqm_gRebvBFGCAXiirz24YN514fupq1BUvYDv_O8HjfTpQ@mail.gmail.com>
From: Costin Manolache <costin@gmail.com>
To: Brian Raymor <Brian.Raymor@microsoft.com>
Content-Type: multipart/alternative; boundary=001a1140f400211271052bfc641b
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/j_IyD405exey0Xp6oMdCca0IzIo>
Cc: Costin Manolache <costin@google.com>, "webpush@ietf.org" <webpush@ietf.org>
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: Wed, 17 Feb 2016 19:38:17 -0000

On Tue, Feb 16, 2016 at 2:44 PM, Brian Raymor <Brian.Raymor@microsoft.com>
wrote:

>
> On Sat, Feb 6, 2016 at 12:48 PM, Costin Manolache <costin@gmail.com>
> wrote:
>
> > I assume 202 (Accepted) would be better for TTL=0 if the service is not
> actually storing the message.
>
> My reading of 202 (Accepted) is that it's intended for asynchronous
> operations:
>
> http://tools.ietf.org/html/rfc7231#section-6.3.3
>
>    The 202 response is intentionally noncommittal.  Its purpose is to
>    allow a server to accept a request for some other process (perhaps a
>    batch-oriented process that is only run once per day) without
>    requiring that the user agent's connection to the server persist
>    until the process is completed.  The representation sent with this
>    response ought to describe the request's current status and point to
>    (or embed) a status monitor that can provide the user with an
>    estimate of when the request will be fulfilled.
>
>
This is pretty much what webpush is doing - accepts the request, and some
other
process ( the connection side ) may deliver it later :-)
However it may be confusing, so I'm fine either way.



> I suggest that we require the TTL -
> https://github.com/webpush-wg/webpush-protocol/issues/76 -
> but maintain the current behavior where a Location is returned even for
> TTL=0.   There are already
> special cases in the text for TTL=0 indicating that the resource may be
> deleted before the user agent can
> acknowledge a message.
>

+1


Costin


> As I noted in my earlier response to Ben, the Location resource is also
> subsequently required for the
> synthesized GET:
>
> https://tools.ietf.org/html/draft-ietf-webpush-protocol-03#section-7.1
>
>    Each push message is pushed as the response to a synthesized GET
>    request sent in a PUSH_PROMISE.  This GET request is made to the push
>    message resource that was created by the push service when the
>    application server requested message delivery.
>
> ...Brian
>
> _______________________________________________
> Webpush mailing list
> Webpush@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush
>

v2.8.7 | Report a Bug | By Email