Re: [Webpush] RFC 8030 on Generic Event Delivery Using HTTP Push

JR Conlin <jconlin@mozilla.com> Thu, 08 December 2016 22:26 UTC

Return-Path: <jconlin@mozilla.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 EAD3C129AD6 for <webpush@ietfa.amsl.com>; 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 <webpush@ietfa.amsl.com>; 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 <webpush@ietf.org>; Thu, 8 Dec 2016 14:24:09 -0800 (PST)
Received: by mail-wj0-x236.google.com with SMTP id tg4so143979wjb.1 for <webpush@ietf.org>; 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 <jconlin@mozilla.com>
Date: Thu, 8 Dec 2016 14:24:07 -0800
Message-ID: <CA+XEteMA+MDRRQwJfh=+E6bzc+KP_O-X2E3BP7VT3EK7VJxAuw@mail.gmail.com>
To: "webpush@ietf.org" <webpush@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b66f18f89638105432d1846
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/FvKqEDqwvIdxW4W1aGUcB-Cx4vw>
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 <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, 08 Dec 2016 22:26:54 -0000

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, <rfc-editor@rfc-editor.org> 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
>