[Webpush] RFC 8292 on Voluntary Application Server Identification (VAPID) 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 []) by ietfa.amsl.com (Postfix) with ESMTP id CDCE9128CFF; Wed, 29 Nov 2017 12:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id U024bczPiB-E; Wed, 29 Nov 2017 12:40:47 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D9A9128BB7; Wed, 29 Nov 2017 12:40:47 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E9C90B80E15; Wed, 29 Nov 2017 12:40:35 -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: <20171129204035.E9C90B80E15@rfc-editor.org>
Date: Wed, 29 Nov 2017 12:40:35 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/5CseeYa34BAHtk3Egufn8QIgckU>
Subject: [Webpush] =?utf-8?q?RFC_8292_on_Voluntary_Application_Server_Iden?= =?utf-8?q?tification_=28VAPID=29_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:50 -0000

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

        RFC 8292

        Title:      Voluntary Application Server Identification (VAPID) 
                    for Web Push 
        Author:     M. Thomson,
                    P. Beverloo
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2017
        Mailbox:    martin.thomson@gmail.com, 
        Pages:      14
        Characters: 30106
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-webpush-vapid-04.txt

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

        DOI:        10.17487/RFC8292

An application server can use the Voluntary Application Server
Identification (VAPID) method described in this document to
voluntarily identify itself to a push service.  The "vapid"
authentication scheme allows a client to include its identity in a
signed token with requests that it makes.  The signature can be used
by the push service to attribute requests that are made by the same
application server to a single entity.  The identification
information can allow the operator of a push service to contact the
operator of the application server.  The signature can be used to
restrict the use of a push message subscription to a single
application server.

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

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