[Webpush] RFC 8291 on Message Encryption for Web Push

rfc-editor@rfc-editor.org Wed, 29 November 2017 20:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 9CC54126C83; Wed, 29 Nov 2017 12:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 WUR35ANUNbBM; Wed, 29 Nov 2017 12:40:42 -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 D32AD1200CF; Wed, 29 Nov 2017 12:40:42 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 422BAB80E0F; Wed, 29 Nov 2017 12:40:31 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, webpush@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20171129204031.422BAB80E0F@rfc-editor.org>
Date: Wed, 29 Nov 2017 12:40:31 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/ugB81jzgPbim3oevEoxXg5n2-4E>
Subject: [Webpush] =?utf-8?q?RFC_8291_on_Message_Encryption_for_Web_Push?=
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 29 Nov 2017 20:40:44 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8291

        Title:      Message Encryption for Web Push 
        Author:     M. Thomson
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2017
        Mailbox:    martin.thomson@gmail.com
        Pages:      13
        Characters: 25780
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-webpush-encryption-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8291

        DOI:        10.17487/RFC8291

This document describes a message encryption scheme for the Web Push
protocol.  This scheme provides confidentiality and integrity for
messages sent from an application server to a user agent.

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