Push Notification with the Session Initiation Protocol (SIP)
draft-holmberg-sipcore-sip-push-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-10-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SIPCORE Working Group                                        C. Holmberg
Internet-Draft                                                  Ericsson
Updates: 4028 (if approved)                              October 9, 2017
Intended status: Standards Track
Expires: April 12, 2018

      Push Notification with the Session Initiation Protocol (SIP)
                   draft-holmberg-sipcore-sip-push-00

Abstract

   This document describes how push notification mechanisms can be used
   to wake up idle Session Initiation Protocol (SIP) applications, in
   order to be able to receive and process SIP requests.  The document
   defines new SIP URI parameters, that can be used in a SIP REGISTER
   request to provide push notification information from the SIP User
   Agent (UA) to the SIP entity (realized as a SIP proxy in this
   document) that will send a push request to the push server in order
   to trigger a push notification towards the SIP UA.

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 April 12, 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
   carefully, as they describe your rights and restrictions with respect

Holmberg                 Expires April 12, 2018                 [Page 1]
Internet-Draft             Session timer glare              October 2017

   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
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Push Resource ID (PRID) . . . . . . . . . . . . . . . . . . .   5
   4.  SIP User Agent (UA) Behavior  . . . . . . . . . . . . . . . .   5
   5.  SIP Proxy Behavior  . . . . . . . . . . . . . . . . . . . . .   6
   6.  Network Address Translator (NAT) Considerations . . . . . . .   6
   7.  Security considerations . . . . . . . . . . . . . . . . . . .   6
   8.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  pn-token  . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.2.  pn-type . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.3.  pn-enckey . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.4.  pn-enccode  . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative references  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative references  . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   In order to save resources (e.g, battery life) some devices and
   operating systems require idle applications to be woken up using a
   push notification service.  Typically each operating system uses a
   dedicated push notification service.  For example, Apple iOS devices
   use the Apple Push Notification Service (APNS).

   Due to the restriction above, applications can not be woken up by
   non-push notification traffic.  This means that an idle Session
   Initiation Protocol (SIP) [RFC3261] User Agent (UA) will not be able
   to receive an incoming SIP request, e.g., an SIP INVITE request
   initiating a new SIP session.

   This document describes how push notification mechanisms can be used
   to wake up idle SIP applications, in order to be able to receive and
   process SIP requests.  The document defines new SIP URI parameters,
   that can be used in a SIP REGISTER request to provide push
   notification information from the SIP UA to the SIP entity (realized
   as a SIP proxy in this document) that will send a push request to the
   push server in order to trigger a push notification towards the SIP
   UA.

Holmberg                 Expires April 12, 2018                 [Page 2]
Internet-Draft             Session timer glare              October 2017
Show full document text