Re: [Webpush] Non-blocking comments on -05

Martin Thomson <martin.thomson@gmail.com> Thu, 02 June 2016 02:13 UTC

Return-Path: <martin.thomson@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 AFA6612D64C for <webpush@ietfa.amsl.com>; Wed, 1 Jun 2016 19:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 A_r7e6_pZyij for <webpush@ietfa.amsl.com>; Wed, 1 Jun 2016 19:13:40 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (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 03EFD12D63D for <webpush@ietf.org>; Wed, 1 Jun 2016 19:13:40 -0700 (PDT)
Received: by mail-qg0-x231.google.com with SMTP id 52so52373589qgy.0 for <webpush@ietf.org>; Wed, 01 Jun 2016 19:13:39 -0700 (PDT)
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; bh=vB+i7WGr3BgA5UanthtlWwEZuKihurzvFIHWcv17vAc=; b=mJiGBsl0AYCw+2k/jpIpeXAxoX5zf4LOjw7a2zW9kRiDfD10H/r9QfOSQCoZOL64t/ QuFZ4jMr6EmDWkJu2Ysid/vL6N5UYEKR2LBLDEAXJ+VtXdMaYQAX03GiZPXJLc7RHe+x GEx6OOZiiMM9//Scq2xDWjW4w8CHOpAw2Jg0D1f82er+KYqBpXFNI8tSnXHWO/USaJBH PeW+PC9Fm+7M1nbFPza238re0oT+vc6nPWkAyDEEXo5C7ayl84pWzE218LiTWfFAiYU1 VsFH9KXAu/i5pIRYcROOdg/IWckSy/5mX/3KVkzfKm6tmOsTBKvJ4g7tn1okmtJzOjsV w9Xg==
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; bh=vB+i7WGr3BgA5UanthtlWwEZuKihurzvFIHWcv17vAc=; b=dIxd7fTioAT+7HDS/wsMu4FiKjD3SzpUYuFOZ4hR5eiJ7/EY27SUi4BE+HVoDgUtNK JfsfK0r5EkBf2b6qu5S0AG8Tt1qTUysiuz7+28rB0Um9yR7jtKHJzQmCmnRpeip9p9BS 6zrdjrCGs5Y3yJ2URzTPxfBujuWneFn81i/0CG1jgL6CLC/xY6TfHmiY75ImbeYTEH3V jHy7pshj787D75Tvm5uiwP4q38A3Kc+Rsp3yaBi6LknpnzhPomTXEYdyuieg5mVR9eyd 3/oC5/JBfirjiTiBGoE3Xxux+ro5M6+CZVKxqtOi4N3ti6GfNR5VgAKGs8Wq0FWzIT0d JQvw==
X-Gm-Message-State: ALyK8tIuzYLo/5e3j5dBC6biEcbST16D5vh7nH4/VX3gqGRwitzZQlN7Reknkt/CxhVxs+6JjSdnT6ArB2pE3Q==
MIME-Version: 1.0
X-Received: by 10.140.163.212 with SMTP id j203mr40806449qhj.40.1464833619148; Wed, 01 Jun 2016 19:13:39 -0700 (PDT)
Received: by 10.140.104.110 with HTTP; Wed, 1 Jun 2016 19:13:39 -0700 (PDT)
In-Reply-To: <6af49c2baf1b4e4f884b812d573b947e@Antiope.crf.canon.fr>
References: <CALt3x6=_yc9TegOut_g+6W5fvhP7sfW+_gwRZnEVFA5PNgER6Q@mail.gmail.com> <6af49c2baf1b4e4f884b812d573b947e@Antiope.crf.canon.fr>
Date: Thu, 2 Jun 2016 12:13:39 +1000
Message-ID: <CABkgnnWebfxnPOLMXK+n+2G=c8DOG4Eb4AWMsWXJmmdnE4pUwg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/MRMmZu7qEsVQx_dEepgrCDxP02U>
Cc: "webpush@ietf.org" <webpush@ietf.org>, Peter Beverloo <beverloo@google.com>
Subject: Re: [Webpush] Non-blocking comments on -05
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: Thu, 02 Jun 2016 02:13:42 -0000

On 1 June 2016 at 21:46, RUELLAN Herve <Herve.Ruellan@crf.canon.fr> wrote:
> 2. What does a push server that receives a request for a push message with "Prefer: respond-async" but doesn't want to provide a receipt subscription, or doesn't support providing receipts? Is this allowed in the first place?

This is handled in RFC7240.  It ignores the Prefer header.  I believe
that existing implementations do this very well :)