RFC 8030 on Generic Event Delivery Using HTTP Push

rfc-editor@rfc-editor.org Thu, 08 December 2016 16:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@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
Subject: RFC 8030 on Generic Event Delivery Using HTTP Push
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161208164203.94881B80232@rfc-editor.org>
Date: Thu, 08 Dec 2016 08:42:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/p3mMfuwpPa-ubITbGrfoRWJlKAs>
Cc: drafts-update-ref@iana.org, webpush@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=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