Use of VAPID in JMAP WebPush
draft-ietf-jmap-webpush-vapid-10

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>, brong@fastmailteam.com, draft-ietf-jmap-webpush-vapid@ietf.org, jmap-chairs@ietf.org, jmap@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Protocol Action: 'Use of VAPID in JMAP WebPush' to Proposed Standard (draft-ietf-jmap-webpush-vapid-04.txt)

The IESG has approved the following document:
- 'Use of VAPID in JMAP WebPush'
  (draft-ietf-jmap-webpush-vapid-04.txt) as Proposed Standard

This document is the product of the JSON Mail Access Protocol Working Group.

The IESG contact persons are Murray Kucherawy and Orie Steele.

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

Ballot Text

Technical Summary

   This document defines a method for JMAP servers to advertise their
   capability to authenticate WebPush notifications using the Voluntary
   Application Server Identification protocol.

Working Group Summary

   JMAP is a small working group, there's wide consensus that this is a good idea
   and quite a few people were vocal in the discussion.

   There was one issue that caused a delay and repeat working-group-last-call
   however it was resolved to the satisfaction of all.

Document Quality

   All users of JMAP push either have or will have to implement this, as browsers are
   requiring it.

   The related working group (webpush) has concluded, however this document has been
   discussed with one of the authors of the related document (rfc8292).

   No particular directorate reviews are required or outstanding.

Personnel

   The Document Shepherd for this document is Bron Gondwana. The
   Responsible Area Director is Murray Kucherawy.

RFC Editor Note