[Webpush] What to push?
Anton Tveretin <tveretinas@yandex.ru> Mon, 30 May 2016 21:35 UTC
Return-Path: <tveretinas@yandex.ru>
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 D30CE12D1E5 for <webpush@ietfa.amsl.com>; Mon, 30 May 2016 14:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 (1024-bit key) header.d=yandex.ru
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 opqy7mbPP9rg for <webpush@ietfa.amsl.com>; Mon, 30 May 2016 14:35:27 -0700 (PDT)
Received: from forward16p.cmail.yandex.net (forward16p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::bf]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8617E12D667 for <webpush@ietf.org>; Mon, 30 May 2016 14:35:27 -0700 (PDT)
Received: from mxback6g.mail.yandex.net (mxback6g.mail.yandex.net [77.88.29.167]) by forward16p.cmail.yandex.net (Yandex) with ESMTP id 036252114E for <webpush@ietf.org>; Tue, 31 May 2016 00:35:23 +0300 (MSK)
Received: from web18g.yandex.ru (web18g.yandex.ru [95.108.252.118]) by mxback6g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id xCeWyxoZw9-ZNWWUjlM; Tue, 31 May 2016 00:35:23 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1464644123; bh=LK+t69uxO1Dh9Q2IrqkliUQ87fjdzSvRFEOvWo6Vg/Q=; h=X-Yandex-Sender-Uid:From:To:Subject:MIME-Version:Message-Id: X-Mailer:Date:Content-Transfer-Encoding:Content-Type; b=UZD3MVHzOcQHPbTBzhD0JvLtx7GTHsKF7aVMTUDo/Q5PsLTBx1/bdUqJxlB7BVUqN cID3A5ujzZ8xzUOVg1wBoq+O+Xf9huhibcY9jWN2fJ78LfPAAiVFOkrH1EOZcFfp28 ob7DSsBRnCBjeQPvGfrkN9e1fXBlOiizx9XIa9Qs=
Authentication-Results: mxback6g.mail.yandex.net; dkim=pass header.i=@yandex.ru
X-Yandex-Suid-Status: 1 0,1 492863893
X-Yandex-Sender-Uid: 161206619
Received: by web18g.yandex.ru with HTTP; Tue, 31 May 2016 00:35:23 +0300
From: Anton Tveretin <tveretinas@yandex.ru>
To: webpush@ietf.org
MIME-Version: 1.0
Message-Id: <1140911464644123@web18g.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Tue, 31 May 2016 02:35:23 +0500
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/Al5xy2qQOBxXMrnE-SCKjUt-SJU>
Subject: [Webpush] What to push?
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: Mon, 30 May 2016 21:35:30 -0000
Hello All, I want to discuss what kind of information could be HTTP-pushed. For instance, HTML 6.0 once suggested to provide changes (delta) of the document. Maybe this does not fit well into current HTTP 2.0 spec - a new frame type is needed. I am not the author of HTML 6.0 (D. Tyurin is). Regards, Anton Tveretin
- [Webpush] What to push? Anton Tveretin
- Re: [Webpush] What to push? Martin Thomson