Voluntary Application Server Identification (VAPID) for Web Push
draft-ietf-webpush-vapid-04

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, adam@nostrum.com, draft-ietf-webpush-vapid@ietf.org, Phil Sorber <sorber@apache.org>, sorber@apache.org, webpush-chairs@ietf.org, webpush@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Voluntary Application Server Identification (VAPID) for Web Push' to Proposed Standard (draft-ietf-webpush-vapid-04.txt)

The IESG has approved the following document:
- 'Voluntary Application Server Identification (VAPID) for Web Push'
  (draft-ietf-webpush-vapid-04.txt) as Proposed Standard

This document is the product of the Web-Based Push Notifications Working
Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-webpush-vapid/

Ballot Text

Technical Summary

   An application server can use the method described to voluntarily
   identify itself to a push service.  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.  An application
   server can include additional information that the operator of a push
   service can use to contact the operator of the application server.
   This identification information can be used to restrict the use of a
   push subscription a single application server.

Working Group Summary

  There is nothing notable about this document's progress through the working group.

Document Quality

  Both Google and Mozilla have deployed VAPID as part of their webpush solutions.

Personnel

  Phil Sorber is the document shepherd. Adam Roach is the responsible AD.

RFC Editor Note