From nobody Thu Dec 8 08:42:10 2016 Return-Path: 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 620661295EF; Thu, 8 Dec 2016 08:42:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -107.098 X-Spam-Level: X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no 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 AHjHXK5LdECs; Thu, 8 Dec 2016 08:42:03 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98D38129489; Thu, 8 Dec 2016 08:42:03 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 94881B80232; Thu, 8 Dec 2016 08:42:03 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161208164203.94881B80232@rfc-editor.org> Date: Thu, 8 Dec 2016 08:42:03 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, webpush@ietf.org, rfc-editor@rfc-editor.org Subject: [Webpush] RFC 8030 on Generic Event Delivery Using HTTP 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2016 16:42:05 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8030 Title: Generic Event Delivery Using HTTP Push Author: M. Thomson, E. Damaggio, B. Raymor, Ed. Status: Standards Track Stream: IETF Date: December 2016 Mailbox: martin.thomson@gmail.com, elioda@microsoft.com, brian.raymor@microsoft.com Pages: 31 Characters: 68069 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-webpush-protocol-12.txt URL: https://www.rfc-editor.org/info/rfc8030 DOI: 10.17487/RFC8030 This document describes a simple protocol for the delivery of real- time events to user agents. This scheme uses HTTP/2 server push. This document is a product of the Web-Based Push Notifications Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Thu Dec 8 14:26:56 2016 Return-Path: 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 EAD3C129AD6 for ; Thu, 8 Dec 2016 14:26:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 yLPh35WSG0FQ for ; Thu, 8 Dec 2016 14:26:51 -0800 (PST) Received: from mail-wj0-x236.google.com (mail-wj0-x236.google.com [IPv6:2a00:1450:400c:c01::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 90BF4129AF6 for ; Thu, 8 Dec 2016 14:24:09 -0800 (PST) Received: by mail-wj0-x236.google.com with SMTP id tg4so143979wjb.1 for ; Thu, 08 Dec 2016 14:24:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=nWm0BlC8PAMHS0JFbSOUsp0HKVS5GWbxkOhi0CT6IEA=; b=dlEfOwg/DKUUCX26IKHTmOLNxIcNf1zoGEpfKdGTGX56tVIsR+olpyZ7+q3eMuJfsK Y6y/MtX3hm+hEns6o71Qu0acXbyWpvFaVv0OIRUYxiaDtsNFa0XN3MpmYcnHMDJSkFU7 JPXqwjU/QTJO3zYd2SE7ucrt7AIPD7wDl5h90= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=nWm0BlC8PAMHS0JFbSOUsp0HKVS5GWbxkOhi0CT6IEA=; b=Kn/Pdypl2s7dux3bjabAVseapw20GcJGAmr0aSs8OhL6pNMLRZXCBHRirQdf92ERDx fz5VQvLzzX9S0XE3nnK5Tl2v/IfXs8Bs8sUl6qt1CXYLQ0kfrR/U1iEqLPaiBSiZYlCD 5T2OZg0GZf7WUPynKlPyx8U6Kaxqkz0PzUWdu+N8h13wHxKn49qDIobosAwUG5eqE3RH hHICwp/ZMc0ZoiDylknXhcwnOfLKxPllZKJFdgSnOWYyXMxiunMIoRH5L4umpJGuJWIx CfbIpCMjDcr+sVvj1Hnjtt2HfDMUAX4MslYjg8OYr6CxPQhZk5udPRQQptMcZdLTx7Pk Kx5w== X-Gm-Message-State: AKaTC029hYWplOFOpHyb3pdHlfyG0rbW5dxXzJjT+Rin4mReMTR6Iq9TlnZdz2AapvZP7Y1FJyXq4GoHCQNMpZ0I X-Received: by 10.194.14.105 with SMTP id o9mr66043887wjc.66.1481235847787; Thu, 08 Dec 2016 14:24:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.24.74 with HTTP; Thu, 8 Dec 2016 14:24:07 -0800 (PST) In-Reply-To: <20161208164203.94881B80232@rfc-editor.org> References: <20161208164203.94881B80232@rfc-editor.org> From: JR Conlin Date: Thu, 8 Dec 2016 14:24:07 -0800 Message-ID: To: "webpush@ietf.org" Content-Type: multipart/alternative; boundary=047d7b66f18f89638105432d1846 Archived-At: Subject: Re: [Webpush] RFC 8030 on Generic Event Delivery Using HTTP Push X-BeenThere: webpush@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: jrconlin@mozilla.com List-Id: Discussion of potential IETF work on a web push protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2016 22:26:54 -0000 --047d7b66f18f89638105432d1846 Content-Type: text/plain; charset=UTF-8 Congrats to the authors, editors and all involved, and huge thanks for the months of work that went into this. One of a very few number of highlights to this year. On Thu, Dec 8, 2016 at 8:42 AM, wrote: > A new Request for Comments is now available in online RFC libraries. > > > RFC 8030 > > Title: Generic Event Delivery Using HTTP Push > Author: M. Thomson, > E. Damaggio, > B. Raymor, Ed. > Status: Standards Track > Stream: IETF > Date: December 2016 > Mailbox: martin.thomson@gmail.com, > elioda@microsoft.com, > brian.raymor@microsoft.com > Pages: 31 > Characters: 68069 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-webpush-protocol-12.txt > > URL: https://www.rfc-editor.org/info/rfc8030 > > DOI: 10.17487/RFC8030 > > This document describes a simple protocol for the delivery of real- > time events to user agents. This scheme uses HTTP/2 server push. > > This document is a product of the Web-Based Push Notifications Working > Group of the IETF. > > This is now a Proposed Standard. > > STANDARDS TRACK: This document specifies an Internet Standards Track > protocol for the Internet community, and requests discussion and > suggestions > for improvements. Please refer to the current edition of the Official > Internet Protocol Standards (https://www.rfc-editor.org/standards) for the > standardization state and status of this protocol. Distribution of this > memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > https://www.ietf.org/mailman/listinfo/ietf-announce > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see https://www.rfc-editor.org/search > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > Webpush mailing list > Webpush@ietf.org > https://www.ietf.org/mailman/listinfo/webpush > --047d7b66f18f89638105432d1846 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Congrats to the authors, editors and all involved, and huge thanks for t= he months of work that went into this.

One of a very few number of highlight= s to this year.

On Thu, Dec 8, 2016 at 8:42 AM, <rfc-editor@rfc-edi= tor.org> wrote:
A new Reque= st for Comments is now available in online RFC libraries.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 8030

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 Generic Event Delive= ry Using HTTP Push
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author:=C2=A0 =C2=A0 =C2=A0M. Thomson,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 E. Da= maggio,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 B. Ra= ymor, Ed.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0Standards Track
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stream:=C2=A0 =C2=A0 =C2=A0IETF
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date:=C2=A0 =C2=A0 =C2=A0 =C2=A0December 2016 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mailbox:=C2=A0 =C2=A0 martin.thomson@gmail.com,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 elioda@microsoft.com,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 brian.raymor@microsoft.com
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 31
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Characters: 68069
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Updates/Obsoletes/SeeAlso:=C2=A0 =C2=A0None

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I-D Tag:=C2=A0 =C2=A0 draft-ietf-webpush-protoc= ol-12.txt

=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 h= ttps://www.rfc-editor.org/info/rfc8030

=C2=A0 =C2=A0 =C2=A0 =C2=A0 DOI:=C2=A0 =C2=A0 =C2=A0 =C2=A0 10.17487/RFC803= 0

This document describes a simple protocol for the delivery of real-
time events to user agents.=C2=A0 This scheme uses HTTP/2 server push.

This document is a product of the Web-Based Push Notifications Working Grou= p of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestion= s
for improvements.=C2=A0 Please refer to the current edition of the Official=
Internet Protocol Standards (https://www.rfc-editor.org/sta= ndards) for the
standardization state and status of this protocol.=C2=A0 Distribution of th= is
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
=C2=A0 https://www.ietf.org/mailman/listinf= o/ietf-announce
=C2=A0 https://mailman.rfc-editor.org/m= ailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/s= earch
For downloading RFCs, see https://www.rfc-editor.org/re= trieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.=C2=A0 Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
Webpush mailing list
Webpush@ietf.org
https://www.ietf.org/mailman/listinfo/webpush<= br>

--047d7b66f18f89638105432d1846-- From nobody Wed Dec 21 21:43:01 2016 Return-Path: X-Original-To: webpush@ietf.org Delivered-To: webpush@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68AC81289B0; Wed, 21 Dec 2016 21:42:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148238537939.12692.10265954430889155154.idtracker@ietfa.amsl.com> Date: Wed, 21 Dec 2016 21:42:59 -0800 Archived-At: Cc: webpush@ietf.org Subject: [Webpush] I-D Action: draft-ietf-webpush-encryption-07.txt X-BeenThere: webpush@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussion of potential IETF work on a web push protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2016 05:42:59 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web-Based Push Notifications of the IETF. Title : Message Encryption for Web Push Author : Martin Thomson Filename : draft-ietf-webpush-encryption-07.txt Pages : 11 Date : 2016-12-21 Abstract: A message encryption scheme is described for the Web Push protocol. This scheme provides confidentiality and integrity for messages sent from an Application Server to a User Agent. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-webpush-encryption/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-webpush-encryption-07 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-webpush-encryption-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Dec 21 21:44:11 2016 Return-Path: X-Original-To: webpush@ietf.org Delivered-To: webpush@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D05B51289B0; Wed, 21 Dec 2016 21:44:09 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148238544984.12667.6121324633568675475.idtracker@ietfa.amsl.com> Date: Wed, 21 Dec 2016 21:44:09 -0800 Archived-At: Cc: webpush@ietf.org Subject: [Webpush] I-D Action: draft-ietf-webpush-vapid-02.txt X-BeenThere: webpush@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussion of potential IETF work on a web push protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2016 05:44:10 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web-Based Push Notifications of the IETF. Title : Voluntary Application Server Identification for Web Push Authors : Martin Thomson Peter Beverloo Filename : draft-ietf-webpush-vapid-02.txt Pages : 12 Date : 2016-12-21 Abstract: An application server can voluntarily identify itself to a push service using the described technique. This identification information can be used by the push service to attribute requests that are made by the same application server to a single entity. This can used to reduce the secrecy for push subscription URLs by being able to restrict subscriptions to a specific application server. An application server is further able to include additional information that the operator of a push service can use to contact the operator of the application server. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-webpush-vapid/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-webpush-vapid-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-webpush-vapid-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Dec 22 05:47:26 2016 Return-Path: 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 6684B129A09 for ; Thu, 22 Dec 2016 05:47:25 -0800 (PST) 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 drpb6fF4Zc3b for ; Thu, 22 Dec 2016 05:47:24 -0800 (PST) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 AC795129A1B for ; Thu, 22 Dec 2016 05:47:13 -0800 (PST) Received: by mail-qt0-x22a.google.com with SMTP id w33so234744878qtc.3 for ; Thu, 22 Dec 2016 05:47:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=3FpjKeG12ZzseXH3WEgZRRrRlrIQrJ2WYUyfbu38BR0=; b=GAbRwcQPV+Sd15TGFv8T8CPOcrhXe86dwxdhcHDr76Hmo2kC/aHwWAaH8ADPnFczkk Foiy6fvuHyZyCRFEU7rv9kn0mUDl6m1x6MBwJ1m60C6hz1CpmnVCgUTK7cKcVcPkuEaQ 38ZlwBVlNVvcc7E/FxJMhJVFVhhIZm5R8Oiq/xz3+Vxy1d3tV4TBTzxB3nVFcjS+L7wq VBZpd+IbF2CohWOxHzT5imW9MlUpsSGWm3ggpWJAvRZlbZIramaYZz27I3PjuTq2LHr2 Apoo31KTmALas0kR9risNjVL4eQAKgDOF1l5xYyX9+GTABHQHy/9qW9TQq8xLb94uOQW xXng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3FpjKeG12ZzseXH3WEgZRRrRlrIQrJ2WYUyfbu38BR0=; b=byqAOjICoDOWjmanHegfCsp2OBkUaM4tjRYAcuXkmu/chBL5b/DrqRrvR99uKbp/HH ow3KvEeBthoOxRlrqrKipHIuI5r8eViOex5lS29AowzaZcnEdLz1MttjRrtr0RXk6tJS g3yo7zcaPVL36UiX8ftTb5Wq23R9OFOYVTCmiP1hc1pup8GhmRs13FrFY8FgxnDMxc0w r+VhkWrixoBh2rcxpmqnGLqZeIAoV/ROWni3B1aWTr82f0cp8AjXqAhd3wrFkXwgW+5y 7hazDXGhz+/IjkyCSZhQWFX1wp1tEE9Xdw1d+aQJWcu6WtzsRdKML+bnIjz2uvVry3IS 8DdQ== X-Gm-Message-State: AIkVDXIO2MgDDNqncVVY6WS2uNcaf2BF158puhgaEFx8qLSBoUFiWvlDuc+nrKXor1UOBQ4QX/zpxOUQ74qSzA== X-Received: by 10.237.44.161 with SMTP id g30mr9971536qtd.144.1482414432743; Thu, 22 Dec 2016 05:47:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.38.233 with HTTP; Thu, 22 Dec 2016 05:47:12 -0800 (PST) From: Martin Thomson Date: Fri, 23 Dec 2016 00:47:12 +1100 Message-ID: To: "webpush@ietf.org" Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [Webpush] New encryption and vapid drafts 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2016 13:47:25 -0000 After a burst of activity in November, we had a few fairly significant updates to these documents. Most significant is the changes to the base document in the HTTP working group. Now that that has settled down, I've merged the PRs and submitted new versions. Bad news is that I forgot something in the HTTP doc, so there will be a new version of encryption. It's minor, but important enough to catch in a new revision. I'll get to that within 24 hours. From nobody Thu Dec 22 18:49:51 2016 Return-Path: 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 815851294BF for ; Thu, 22 Dec 2016 18:49:50 -0800 (PST) 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 HhCH4eLo7TXn for ; Thu, 22 Dec 2016 18:49:49 -0800 (PST) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 67B0A129468 for ; Thu, 22 Dec 2016 18:49:49 -0800 (PST) Received: by mail-qk0-x22c.google.com with SMTP id u25so121828092qki.2 for ; Thu, 22 Dec 2016 18:49:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=GVttNGWyd88BaeAxnzUF5E24DIVfg1YUMYKuYIFq+5Y=; b=JPxGPOrFj7dy/QtGtcttk8P7ZZguNcgTlpqsoaije+1VTn/P3f4zPfxtONLBfkIjXc Xn/uMWpg3XnEZf/DNtb8ha4750Y2mOkkLe/+3wW+uC/wZwHmBto8PE0LUVKgjWrKOkJT k8Yp4fbYykENia9M6cIYgRY4pyPkJacfXRRuFKi6MgO67ES3jVTjNHLGpvi71ls5/HrP wpfEN0gEREVSrPXbMpqUzfe9UVQKlBJ69EA8Vz0rjYdOjhtOL7QKnR9vt/vpDBQU61yc M8lC5+i2HBvbE+0up4AbG4oxy0P+VG1hc4JWnP5G4pHRdFl9VUFxCY/T6Z9LdTaYyGm6 pefQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=GVttNGWyd88BaeAxnzUF5E24DIVfg1YUMYKuYIFq+5Y=; b=O9OXHmFYzNqGDM3zFjSPNmsaMyU4j8S2Qk3IQ8JZa/f/TtXSUNa4eipUhN/jQnV/vU ozpH+AY/lBaAN5bIRLA5AeQ4+Y5YlL3Jkn0gJQBffoGPW/VhN97X/jbq1ehsq25VpGYL av6ft4CvnLmKFWpA65nSXahOtrgE582tIUDplVHLda5ar2HbFsPGdyiFca+rrOr5Xaqy fuYQlrrA/uu4yWB8a30sjCrpI7ZijFv15eSg0ZqZ8rQ2Ej13+MKJ/tXHkil1d+CzXC2G 4k2GhBmGJLrbkooGWD/MwspbNMrFu/6WaOFE6MUOZznUEEn7r8IVz6Q1b4n6DdYJrrOY EEyQ== X-Gm-Message-State: AIkVDXJs/IIbEKIEburW480Z5m7DEzm+gu30mL0GkCUn7PL3BpD78jSS+Lg9HY9CdAUFHyMNVCBbhUWxFYs8fA== X-Received: by 10.55.74.77 with SMTP id x74mr11405623qka.316.1482461388516; Thu, 22 Dec 2016 18:49:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.38.233 with HTTP; Thu, 22 Dec 2016 18:49:48 -0800 (PST) In-Reply-To: References: From: Martin Thomson Date: Fri, 23 Dec 2016 13:49:48 +1100 Message-ID: To: "webpush@ietf.org" Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: Re: [Webpush] New encryption and vapid drafts 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2016 02:49:50 -0000 As it turns out, I should avoid writing specs while tired. The webpush drafts are unaffected by the changes to the HTTP specs. Since I'm here, the library that I maintain will soon implement the latest version. I'm updating the record size handling right now. On 23 December 2016 at 00:47, Martin Thomson wrote: > After a burst of activity in November, we had a few fairly significant > updates to these documents. Most significant is the changes to the > base document in the HTTP working group. > > Now that that has settled down, I've merged the PRs and submitted new versions. > > Bad news is that I forgot something in the HTTP doc, so there will be > a new version of encryption. It's minor, but important enough to > catch in a new revision. I'll get to that within 24 hours.