Push Notification with the Session Initiation Protocol (SIP)
draft-ietf-sipcore-sip-push-24

Document Type Active Internet-Draft (sipcore WG)
Last updated 2019-01-22
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 Brian Rosen
Shepherd write-up Show (last changed 2018-10-26)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Has 2 DISCUSSes. Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Ben Campbell
Send notices to Brian Rosen <br@brianrosen.net>
IANA IANA review state Version Changed - Review Needed
IANA action state None
SIPCORE Working Group                                        C. Holmberg
Internet-Draft                                                  Ericsson
Intended status: Standards Track                               M. Arnold
Expires: July 26, 2019                               Metaswitch Networks
                                                        January 22, 2019

      Push Notification with the Session Initiation Protocol (SIP)
                     draft-ietf-sipcore-sip-push-24

Abstract

   This document describes how a Push Notification Service (PNS) can be
   used to wake suspended Session Initiation Protocol (SIP) User Agents
   (UAs), using push notifications, for the UA to be able to send
   binding-refresh REGISTER requests and to receive receive incoming SIP
   requests.  The document defines new SIP URI parameters and new
   feature-capability indicators that can be used in SIP messages to
   indicate support of the mechanism defined in this document, to
   exchange PNS information between the SIP User Agent (UA) and the SIP
   entity that will request that push notifications are sent to the UA,
   and to trigger such push notification requests.

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 July 26, 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Holmberg & Arnold         Expires July 26, 2019                 [Page 1]
Internet-Draft                  SIP PUSH                    January 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Push Resource ID (PRID) . . . . . . . . . . . . . . . . . . .   7
   4.  SIP User Agent (UA) Behavior  . . . . . . . . . . . . . . . .   7
     4.1.  REGISTER  . . . . . . . . . . . . . . . . . . . . . . . .   7
       4.1.1.  Request Push Notifications  . . . . . . . . . . . . .   8
       4.1.2.  Disable Push Notifications  . . . . . . . . . . . . .   9
       4.1.3.  Receive Push Notifications  . . . . . . . . . . . . .  10
       4.1.4.  Sending Binding-Refresh Requests Using Non-Push
               Mechanism . . . . . . . . . . . . . . . . . . . . . .  10
       4.1.5.  Query Network PNS Capabilities  . . . . . . . . . . .  11
   5.  SIP Proxy Behavior  . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  PNS Provider  . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  SIP Request Push Queue  . . . . . . . . . . . . . . . . .  12
     5.3.  SIP URI Comparison Rules  . . . . . . . . . . . . . . . .  12
     5.4.  Indicate Support of Type of PNS . . . . . . . . . . . . .  13
     5.5.  Trigger Periodic Binding Refresh  . . . . . . . . . . . .  13
     5.6.  SIP Requests  . . . . . . . . . . . . . . . . . . . . . .  14
       5.6.1.  REGISTER  . . . . . . . . . . . . . . . . . . . . . .  14
       5.6.2.  Initial Request for Dialog or Stand-Alone Request . .  17
   6.  Support Of Longlived SIP Dialogs  . . . . . . . . . . . . . .  20
     6.1.  SIP UA Behavior . . . . . . . . . . . . . . . . . . . . .  22
       6.1.1.  Initial Request for Dialog  . . . . . . . . . . . . .  22
     6.2.  SIP Proxy Behavior  . . . . . . . . . . . . . . . . . . .  23
       6.2.1.  REGISTER  . . . . . . . . . . . . . . . . . . . . . .  23
       6.2.2.  Initial Request for Dialog  . . . . . . . . . . . . .  23
       6.2.3.  Mid-Dialog Request  . . . . . . . . . . . . . . . . .  24
   7.  Support Of SIP Replaces . . . . . . . . . . . . . . . . . . .  24
   8.  Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . .  25
     8.1.  555 (Push Notification Service Not Supported) Response
           Code  . . . . . . . . . . . . . . . . . . . . . . . . . .  25
Show full document text