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

Document Type Active Internet-Draft (webpush WG)
Last updated 2017-09-03
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Phil Sorber
Shepherd write-up Show (last changed 2017-05-06)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Adam Roach
Send notices to Phil Sorber <sorber@apache.org>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                         M. Thomson
Internet-Draft                                                   Mozilla
Intended status: Standards Track                             P. Beverloo
Expires: March 8, 2018                                            Google
                                                      September 04, 2017

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

Abstract

   An application server can use the method described to voluntarily
   identify itself to a push service.  The "vapid" authentication scheme
   allows a client to include its an 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 subscription to a single application server.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 8, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Thomson & Beverloo        Expires March 8, 2018                 [Page 1]
Internet-Draft             Self Identification            September 2017

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Voluntary Identification  . . . . . . . . . . . . . . . .   3
     1.2.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Application Server Self-Identification  . . . . . . . . . . .   4
     2.1.  Application Server Contact Information  . . . . . . . . .   4
     2.2.  Additional Claims . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Cryptographic Agility . . . . . . . . . . . . . . . . . .   5
     2.4.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Vapid Authentication Scheme . . . . . . . . . . . . . . . . .   6
     3.1.  Token Parameter (t) . . . . . . . . . . . . . . . . . . .   6
     3.2.  Public Key Parameter (k)  . . . . . . . . . . . . . . . .   6
   4.  Subscription Restriction  . . . . . . . . . . . . . . . . . .   7
     4.1.  Creating a Restricted Push Subscription . . . . . . . . .   7
     4.2.  Using Restricted Subscriptions  . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Vapid Authentication Scheme Registration  . . . . . . . .  10
     6.2.  Vapid Authentication Scheme Parameters  . . . . . . . . .  10
     6.3.  application/webpush-options+json Media Type Registration   11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The Web Push protocol [RFC8030] describes how an application server
   is able to request that a push service deliver a push message to a
   user agent.

   As a consequence of the expected deployment architecture, there is no
   basis for an application server to be known to a push service prior
   to requesting delivery of a push message.  Requiring that the push
Show full document text