IETF Logo Mail Archive

Re: [Webpush] Delivery receipts support

Costin Manolache <costin@gmail.com> Sat, 04 June 2016 00:59 UTC

Return-Path: <costin@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 9A04F12D836 for <webpush@ietfa.amsl.com>; Fri, 3 Jun 2016 17:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, 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 3Dexj-D1rjjI for <webpush@ietfa.amsl.com>; Fri, 3 Jun 2016 17:59:21 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 CF9C712D833 for <webpush@ietf.org>; Fri, 3 Jun 2016 17:59:21 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id g64so48629477pfb.2 for <webpush@ietf.org>; Fri, 03 Jun 2016 17:59:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=9E88aBKw9pWXrzWaNSqB8ICB+iK2irJ/30/Srul8LwU=; b=imOJY6SxPtMxEFAygkY+mRk05ugaLW8MCmNS22k5wFXps8kzr7z52uT/RBK2zobGvX qLGTg864f7HteFtJePqcph1HDZ9u7WQqmXTEaoLs311EAAfUioRRa+cBVtAqyc4+lMwF WJO0OT32a/aHwRgqg7vaxX8Wgxotugsb5LZFwYCFTNln1txf0Yma3QRczuvgvlEL/qr/ 8hom6ubOdIIiGPsiVdyqwOeWablHwgkQKb/Jv9umiSM7kF8fY5+mXLuzTOyFfBr5XrPB kbHTPznCSuFPh0KXhNi7DCIUSFl8C/gxaI1ZmHn1VHC0QibFxVq8t0Qg1UsPz0Wp1Gb3 xMHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=9E88aBKw9pWXrzWaNSqB8ICB+iK2irJ/30/Srul8LwU=; b=NOSVWREydur1HmpqQ3a6XHvfyadqkULABOg0YkpigpMkxYOz82HRbHRCbh5CDZl7iQ y3fGiiNieCsyo/QzfRgEpaeoA43fvjWrU3BTDACJavClA4IHdkLDrAHAec43j5tWynvM 4imCjAsR1rvmlEmsTy/xm5eL9gJYBjJEXQSs1SaW9ZkbkbC+iKQ4BWpYEgIClyZ+k3XA Ztpc8Rz/n2pZ5SxVNKZPaEr9+t/MUVgo7KpNv6ucg/gOidwcKAd4c8WW2lKfTDOFAdcI 3/LyJO4o/AYGU6rXigf4D3iu216gB9skqQjbLdzXWcemjjm2GsHi4NKL6PUdRD4PQOF1 mKGQ==
X-Gm-Message-State: ALyK8tL504aMXWc1sNdx/kzN1oD5MeFhYXCJo4v5BEIle8CzOtQzsoQV8rKo+ycLjYdFsJmaGMjE2cKeNzgkOA==
X-Received: by 10.98.67.138 with SMTP id l10mr9271145pfi.59.1465001961378; Fri, 03 Jun 2016 17:59:21 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnWeVS7Kp2Sm_5yLp-5yZoc6fVXWpV=sFdz2VZPHGkmkbQ@mail.gmail.com>
In-Reply-To: <CABkgnnWeVS7Kp2Sm_5yLp-5yZoc6fVXWpV=sFdz2VZPHGkmkbQ@mail.gmail.com>
From: Costin Manolache <costin@gmail.com>
Date: Sat, 04 Jun 2016 00:59:11 +0000
Message-ID: <CAP8-Fq=jX1Co7AJNZct_KQULGPsPZQY49YeeSNrQum97eoyWRQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>, "webpush@ietf.org" <webpush@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0c0fb480d82f05346959ae
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/uXWbEyph4kg26x0vy8-sFY2xYAU>
Subject: Re: [Webpush] Delivery receipts support
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, 04 Jun 2016 00:59:23 -0000

We can accept messages that request receipts - and we do support sending
the
receipts. Just not the receipts that are in the spec :-)

In the past we assumed it's only an issue of getting a raw http2
 framer/stack - but with the issues around flow control it may take a bit
longer.

If it is acceptable to say that accepting messages with receipts is
mandatory, but
using the specific h2+promises receipt monitoring is optional - I think
it's fine.



On Fri, Jun 3, 2016 at 4:19 PM Martin Thomson <martin.thomson@gmail.com>
wrote:

> Costin (on github) said:
> > Since we have open issues with receipts - can we not make it mandatory ?
> It's very unlikely all implementations will be able to support the receipts
> any time soon, at least not as push promises.
>
> We discussed this in the past.  At that time, we decided to make
> support of delivery receipts mandatory.  Do people want to reopen that
> issue?
>
> Note that I don't believe that any implementation currently supports
> receipts.  I had expected that to be a temporary situation, but if
> people expect that this will be a problem, now would be a good time to
> hear of it.
>
> _______________________________________________
> Webpush mailing list
> Webpush@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush
>

v2.8.7 | Report a Bug | By Email