Push Notification with the Session Initiation Protocol (SIP)
RFC 8599

Document Type RFC - Proposed Standard (May 2019; No errata)
Last updated 2019-05-23
Stream IETF
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Brian Rosen
Shepherd write-up Show (last changed 2018-10-26)
IESG IESG state RFC 8599 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to Brian Rosen <br@brianrosen.net>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                       C. Holmberg
Request for Comments: 8599                                      Ericsson
Category: Standards Track                                      M. Arnold
ISSN: 2070-1721                                      Metaswitch Networks
                                                                May 2019

      Push Notification with the Session Initiation Protocol (SIP)

Abstract

   This document describes how a Push Notification Service (PNS) can be
   used to wake a suspended Session Initiation Protocol (SIP) User Agent
   (UA) with push notifications, and it also describes how the UA can
   send binding-refresh REGISTER requests and receive incoming SIP
   requests in an environment in which the UA may be suspended.  The
   document defines new SIP URI parameters to exchange PNS information
   between the UA and the SIP entity that will then request that push
   notifications be sent to the UA.  It also defines the parameters to
   trigger such push notification requests.  The document also defines
   new feature-capability indicators that can be used to indicate
   support of this mechanism.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8599.

Holmberg & Arnold            Standards Track                    [Page 1]
RFC 8599                        SIP PUSH                        May 2019

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   8
   3.  Push Resource ID (PRID) . . . . . . . . . . . . . . . . . . .   8
   4.  SIP User Agent (UA) Behavior  . . . . . . . . . . . . . . . .   9
     4.1.  REGISTER  . . . . . . . . . . . . . . . . . . . . . . . .   9
       4.1.1.  Request Push Notifications  . . . . . . . . . . . . .   9
       4.1.2.  Disable Push Notifications  . . . . . . . . . . . . .  11
       4.1.3.  Receive Push Notifications  . . . . . . . . . . . . .  11
       4.1.4.  Sending Binding-Refresh Requests Using Non-push
               Mechanism . . . . . . . . . . . . . . . . . . . . . .  11
       4.1.5.  Query Network PNS Capabilities  . . . . . . . . . . .  13
   5.  SIP Proxy Behavior  . . . . . . . . . . . . . . . . . . . . .  14
     5.1.  PNS Provider  . . . . . . . . . . . . . . . . . . . . . .  14
     5.2.  SIP Request Push Bucket . . . . . . . . . . . . . . . . .  15
     5.3.  SIP URI Comparison Rules  . . . . . . . . . . . . . . . .  15
     5.4.  Indicate Support of Type of PNS . . . . . . . . . . . . .  15
     5.5.  Trigger Periodic Binding Refresh  . . . . . . . . . . . .  16
     5.6.  SIP Requests  . . . . . . . . . . . . . . . . . . . . . .  17
       5.6.1.  REGISTER  . . . . . . . . . . . . . . . . . . . . . .  17
       5.6.2.  Initial Request for Dialog or Standalone Request  . .  20
   6.  Support of Long-Lived SIP Dialogs . . . . . . . . . . . . . .  23
     6.1.  SIP UA Behavior . . . . . . . . . . . . . . . . . . . . .  25
       6.1.1.  Initial Request for Dialog  . . . . . . . . . . . . .  25
     6.2.  SIP Proxy Behavior  . . . . . . . . . . . . . . . . . . .  25
       6.2.1.  REGISTER  . . . . . . . . . . . . . . . . . . . . . .  25
       6.2.2.  Initial Request for Dialog  . . . . . . . . . . . . .  26
       6.2.3.  Mid-dialog Request  . . . . . . . . . . . . . . . . .  26
   7.  Support of SIP Replaces . . . . . . . . . . . . . . . . . . .  27
   8.  Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . .  28
     8.1.  555 (Push Notification Service Not Supported) Response
           Code  . . . . . . . . . . . . . . . . . . . . . . . . . .  28

Holmberg & Arnold            Standards Track                    [Page 2]
RFC 8599                        SIP PUSH                        May 2019
Show full document text