draft-ietf-sipcore-sip-push-03.txt   draft-ietf-sipcore-sip-push-04.txt 
SIPCORE Working Group C. Holmberg SIPCORE Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track January 4, 2018 Intended status: Standards Track January 12, 2018
Expires: July 8, 2018 Expires: July 16, 2018
Push Notification with the Session Initiation Protocol (SIP) Push Notification with the Session Initiation Protocol (SIP)
draft-ietf-sipcore-sip-push-03 draft-ietf-sipcore-sip-push-04
Abstract Abstract
This document describes how push notification mechanisms can be used This document describes how push notification mechanisms can be used
to wake up suspended Session Initiation Protocol (SIP) User Agents to wake up suspended Session Initiation Protocol (SIP) User Agents
(UAs), in order to be able to receive and generate SIP requests. The (UAs), in order to be able to receive and generate SIP requests. The
document defines new SIP URI parameters, that can be used in a SIP document defines new SIP URI parameters, that can be used in a SIP
REGISTER request to provide push notification information from the REGISTER request to provide push notification information from the
SIP User Agent (UA) to the SIP entity (realized as a SIP proxy in 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 this document) that will send a push request to the push server in
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 8, 2018. This Internet-Draft will expire on July 16, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 23
4. SIP User Agent (UA) Behavior . . . . . . . . . . . . . . . . 5 4. SIP User Agent (UA) Behavior . . . . . . . . . . . . . . . . 5
5. SIP Proxy Behavior . . . . . . . . . . . . . . . . . . . . . 6 5. SIP Proxy Behavior . . . . . . . . . . . . . . . . . . . . . 6
5.1. PNS Provider Information . . . . . . . . . . . . . . . . 6 5.1. PNS Provider Information . . . . . . . . . . . . . . . . 6
5.2. Trigger Periodic Re-registration . . . . . . . . . . . . 6 5.2. Trigger Periodic Re-registration . . . . . . . . . . . . 6
5.3. SIP Request . . . . . . . . . . . . . . . . . . . . . . . 7 5.3. SIP Request . . . . . . . . . . . . . . . . . . . . . . . 7
6. Network Address Translator (NAT) Considerations . . . . . . . 8 6. Network Address Translator (NAT) Considerations . . . . . . . 8
7. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. 555 (Push Notification Service Not Supported) Response 7.1. 555 (Push Notification Service Not Supported) Response
Code . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Code . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.2. sip.pns Feature-Capability Indicator . . . . . . . . . . 8 7.2. sip.pns Feature-Capability Indicator . . . . . . . . . . 8
7.3. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 8 7.3. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 9
8. PNS Registration Requirements . . . . . . . . . . . . . . . . 9 8. PNS Registration Requirements . . . . . . . . . . . . . . . . 9
9. pn-provider, pn-param and pn-prid URI Parameters for Apple 9. pn-provider, pn-param and pn-prid URI Parameters for Apple
Push Notification service . . . . . . . . . . . . . . . . . . 9 Push Notification service . . . . . . . . . . . . . . . . . . 9
10. pn-provider, pn-param and pn-prid URI Parameters for Google 10. pn-provider, pn-param and pn-prid URI Parameters for Google
Firebase Cloud Messaging (FCM) push notification service . . 10 Firebase Cloud Messaging (FCM) push notification service . . 10
11. Security Considerations . . . . . . . . . . . . . . . . . . . 10 11. Security Considerations . . . . . . . . . . . . . . . . . . . 10
12. IANA considerations . . . . . . . . . . . . . . . . . . . . . 11 12. IANA considerations . . . . . . . . . . . . . . . . . . . . . 11
12.1. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 11 12.1. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 11
12.1.1. pn-provider . . . . . . . . . . . . . . . . . . . . 11 12.1.1. pn-provider . . . . . . . . . . . . . . . . . . . . 11
12.1.2. pn-param . . . . . . . . . . . . . . . . . . . . . . 11 12.1.2. pn-param . . . . . . . . . . . . . . . . . . . . . . 11
12.1.3. pn-prid . . . . . . . . . . . . . . . . . . . . . . 11 12.1.3. pn-prid . . . . . . . . . . . . . . . . . . . . . . 11
12.1.4. pn-enckey . . . . . . . . . . . . . . . . . . . . . 12 12.1.4. pn-enckey . . . . . . . . . . . . . . . . . . . . . 12
12.1.5. pn-enccode . . . . . . . . . . . . . . . . . . . . . 12 12.1.5. pn-enccode . . . . . . . . . . . . . . . . . . . . . 12
12.2. SIP Response Code . . . . . . . . . . . . . . . . . . . 12 12.2. SIP Response Code . . . . . . . . . . . . . . . . . . . 12
12.3. SIP Global Feature-Capability Indicator . . . . . . . . 12 12.3. SIP Global Feature-Capability Indicator . . . . . . . . 12
12.4. PNS Sub-registry Establishment . . . . . . . . . . . . . 13 12.4. PNS Sub-registry Establishment . . . . . . . . . . . . . 13
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
14.1. Normative References . . . . . . . . . . . . . . . . . . 14 14.1. Normative References . . . . . . . . . . . . . . . . . . 14
14.2. Informative References . . . . . . . . . . . . . . . . . 14 14.2. Informative References . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
In order to save resources (e.g, battery life) some devices and In order to save resources (e.g, battery life) some devices and
operating systems require suspended Session Initiation Protocol (SIP) operating systems require suspended Session Initiation Protocol (SIP)
User Agents (UAs) [RFC3261] to be woken up using a push notification User Agents (UAs) [RFC3261] to be woken up using a push notification
service. Typically each operating system uses a dedicated push service. Typically each operating system uses a dedicated push
notification service. For example, Apple iOS devices use the Apple notification service. For example, Apple iOS devices use the Apple
Push Notification service (APNs). Push Notification service (APNs).
skipping to change at page 8, line 31 skipping to change at page 8, line 31
The 555 response code is added to the "Server-Error" Status-Code The 555 response code is added to the "Server-Error" Status-Code
definition. 555 (Push Notification Service Not Supported) is used to definition. 555 (Push Notification Service Not Supported) is used to
indicate that the server did not support the push notification indicate that the server did not support the push notification
service specified in a 'pn-provider' SIP URI parameter. service specified in a 'pn-provider' SIP URI parameter.
The use of the SIP 555 response code is defined for SIP REGISTER The use of the SIP 555 response code is defined for SIP REGISTER
responses. Usage with other SIP methods is undefined. responses. Usage with other SIP methods is undefined.
7.2. sip.pns Feature-Capability Indicator 7.2. sip.pns Feature-Capability Indicator
The sip.pns feature-capability indicator is used in a SIP 555 (Push The sip.pns feature-capability indicator is used in a SIP 200 (OK)
Notficiation Service Not Supported) response to indicate which push response or in a 555 (Push Notficiation Service Not Supported)
notification services the sender of the response supports. response to indicate which push notification services the sender of
the response supports.
sip.pns = "<" pns-list ">" pns-fc = "+sip.pns" EQUAL LDQUOT pns-list RDQUOT
pns-list = pns *(COMMA pns) pns-list = pns *(COMMA pns)
pns = pvalue pns = tag-value
; pvalue as defined in RFC 3261 ; tag-value as defined in RFC 3840
The value of the pns is identical to the corresponding pn-provider The value of the pns is identical to the corresponding pn-provider
SIP URI parameter for the push notification service associated with SIP URI parameter for the push notification service associated with
the value. the value.
7.3. SIP URI Parameters 7.3. SIP URI Parameters
The section defines new SIP URI parameters, by extending the grammar The section defines new SIP URI parameters, by extending the grammar
for "uri-parameter" as defined in [RFC3261]. The ABNF is as follows: for "uri-parameter" as defined in [RFC3261]. The ABNF is as follows:
skipping to change at page 13, line 14 skipping to change at page 13, line 14
Name: sip.pns Name: sip.pns
Description: This feature-capability indicator, when included in a Description: This feature-capability indicator, when included in a
Feature-Caps header field of a REGISTER response, indicates that Feature-Caps header field of a REGISTER response, indicates that
the server supports the SIP push mechanism. The value is a list the server supports the SIP push mechanism. The value is a list
of the push notification services supported by the server. of the push notification services supported by the server.
Reference: [RFCXXXX] Reference: [RFCXXXX]
Contact: Christer Holmberg (christer.holmberg@ericsson.com)
12.4. PNS Sub-registry Establishment 12.4. PNS Sub-registry Establishment
This section creates a new sub-registry, "PNS", under the sip- This section creates a new sub-registry, "PNS", under the sip-
parameters registry: http://www.iana.org/assignments/sip-parameters. parameters registry: http://www.iana.org/assignments/sip-parameters.
The purpose of the sub-registry is to register SIP URI pn-provider The purpose of the sub-registry is to register SIP URI pn-provider
values. values.
This sub-registry is defined as a table that contains the following This sub-registry is defined as a table that contains the following
three columns: three columns:
 End of changes. 11 change blocks. 
13 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/