draft-ietf-sipcore-sip-push-08.txt   draft-ietf-sipcore-sip-push-09.txt 
SIPCORE Working Group C. Holmberg SIPCORE Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track M. Arnold Intended status: Standards Track M. Arnold
Expires: September 1, 2018 Metaswitch Networks Expires: September 16, 2018 Metaswitch Networks
February 28, 2018 March 15, 2018
Push Notification with the Session Initiation Protocol (SIP) Push Notification with the Session Initiation Protocol (SIP)
draft-ietf-sipcore-sip-push-08 draft-ietf-sipcore-sip-push-09
Abstract Abstract
This document describes how a Push Notification Service (PNS) can be This document describes how a Push Notification Service (PNS) can be
used to awake suspended Session Initiation Protocol (SIP) User Agents used to awake suspended Session Initiation Protocol (SIP) User Agents
(UAs), for the UA to be able to receive and send SIP requests. The (UAs), for the UA to be able to receive and send SIP requests. The
document defines new SIP URI parameters and new feature-capability document defines new SIP URI parameters and new feature-capability
indicators that can be used in SIP messages to indicate support of indicators that can be used in SIP messages to indicate support of
the mechanism defined in this document, to exchange PNS information the mechanism defined in this document, to exchange PNS information
between the SIP User Agent (UA) and the SIP entity that will request between the SIP User Agent (UA) and the SIP entity that will request
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 September 1, 2018. This Internet-Draft will expire on September 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Push Resource ID (PRID) . . . . . . . . . . . . . . . . . . . 5 3. Push Resource ID (PRID) . . . . . . . . . . . . . . . . . . . 6
4. SIP User Agent (UA) Behavior . . . . . . . . . . . . . . . . 6 4. SIP User Agent (UA) Behavior . . . . . . . . . . . . . . . . 6
5. SIP Proxy Behavior . . . . . . . . . . . . . . . . . . . . . 8 5. SIP Proxy Behavior . . . . . . . . . . . . . . . . . . . . . 8
5.1. PNS Identifier . . . . . . . . . . . . . . . . . . . . . 8 5.1. PNS Identifier . . . . . . . . . . . . . . . . . . . . . 8
5.2. Trigger Periodic Re-registration . . . . . . . . . . . . 8 5.2. Trigger Periodic Re-registration . . . . . . . . . . . . 8
5.3. SIP Request . . . . . . . . . . . . . . . . . . . . . . . 9 5.3. SIP Request . . . . . . . . . . . . . . . . . . . . . . . 9
5.3.1. REGISTER Request . . . . . . . . . . . . . . . . . . 9 5.3.1. REGISTER Request . . . . . . . . . . . . . . . . . . 9
5.3.2. Initial Request for Dialog or Stand-Alone Request . . 10 5.3.2. Initial Request for Dialog or Stand-Alone Request . . 10
6. Network Address Translator (NAT) Considerations . . . . . . . 11 6. Network Address Translator (NAT) Considerations . . . . . . . 12
7. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. 555 (Push Notification Service Not Supported) Response 7.1. 555 (Push Notification Service Not Supported) Response
Code . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Code . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. sip.pns Feature-Capability Indicator . . . . . . . . . . 12 7.2. sip.pns Feature-Capability Indicator . . . . . . . . . . 12
7.3. sip.vapid Feature-Capability Indicator . . . . . . . . . 12 7.3. sip.vapid Feature-Capability Indicator . . . . . . . . . 13
7.4. sip.pnsreg Feature-Capability Indicator . . . . . . . . . 13 7.4. sip.pnsreg Feature-Capability Indicator . . . . . . . . . 13
7.5. sip.pnsreg Media Feature Tag . . . . . . . . . . . . . . 13 7.5. sip.pnsreg Media Feature Tag . . . . . . . . . . . . . . 14
7.6. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 14 7.6. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 14
8. PNS Registration Requirements . . . . . . . . . . . . . . . . 14 8. PNS Registration Requirements . . . . . . . . . . . . . . . . 14
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 . . . . . . . . . . . . . . . . . . 14 Push Notification service . . . . . . . . . . . . . . . . . . 15
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 . . 15 Firebase Cloud Messaging (FCM) push notification service . . 15
11. Security Considerations . . . . . . . . . . . . . . . . . . . 15 11. pn-provider, pn-param and pn-prid URI Parameters for RFC 8030
12. IANA considerations . . . . . . . . . . . . . . . . . . . . . 16 (Generic Event Delivery Using HTTP Push) . . . . . . . . . . 16
12.1. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 16 12. Security Considerations . . . . . . . . . . . . . . . . . . . 16
12.1.1. pn-provider . . . . . . . . . . . . . . . . . . . . 16 13. IANA considerations . . . . . . . . . . . . . . . . . . . . . 17
12.1.2. pn-param . . . . . . . . . . . . . . . . . . . . . . 16 13.1. SIP URI Parameters . . . . . . . . . . . . . . . . . . . 17
12.1.3. pn-prid . . . . . . . . . . . . . . . . . . . . . . 17 13.1.1. pn-provider . . . . . . . . . . . . . . . . . . . . 17
12.2. SIP Response Code . . . . . . . . . . . . . . . . . . . 17 13.1.2. pn-param . . . . . . . . . . . . . . . . . . . . . . 17
12.3. SIP Global Feature-Capability Indicator . . . . . . . . 17 13.1.3. pn-prid . . . . . . . . . . . . . . . . . . . . . . 18
12.3.1. sip.pns . . . . . . . . . . . . . . . . . . . . . . 17 13.2. SIP Response Code . . . . . . . . . . . . . . . . . . . 18
12.3.2. sip.vapid . . . . . . . . . . . . . . . . . . . . . 18 13.3. SIP Global Feature-Capability Indicator . . . . . . . . 18
12.3.3. sip.pnsreg . . . . . . . . . . . . . . . . . . . . . 18 13.3.1. sip.pns . . . . . . . . . . . . . . . . . . . . . . 18
12.4. SIP Media Feature Tag . . . . . . . . . . . . . . . . . 19 13.3.2. sip.vapid . . . . . . . . . . . . . . . . . . . . . 19
12.4.1. sip.pnsreg . . . . . . . . . . . . . . . . . . . . . 19 13.3.3. sip.pnsreg . . . . . . . . . . . . . . . . . . . . . 19
12.5. PNS Sub-registry Establishment . . . . . . . . . . . . . 20 13.4. SIP Media Feature Tag . . . . . . . . . . . . . . . . . 20
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 13.4.1. sip.pnsreg . . . . . . . . . . . . . . . . . . . . . 20
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 13.5. PNS Sub-registry Establishment . . . . . . . . . . . . . 21
14.1. Normative References . . . . . . . . . . . . . . . . . . 21
14.2. Informative References . . . . . . . . . . . . . . . . . 22 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
15.1. Normative References . . . . . . . . . . . . . . . . . . 22
15.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
In order to save resources (e.g., battery life) some devices In order to save resources (e.g., battery life) some devices
(especially mobile devices) and operating systems will suspend (especially mobile devices) and operating systems will suspend
applications when not used. In some cases, internal timers cannot be applications when not used. In some cases, internal timers cannot be
used to awake such applications, nor will incoming network traffic used to awake such applications, nor will incoming network traffic
awake the application. Instead, the only way to awake the awake the application. Instead, the only way to awake the
application is by using a Push Notification Service (PNS). Typically application is by using a Push Notification Service (PNS). Typically
each operating system uses a dedicated PNS. For example, Apple iOS each operating system uses a dedicated PNS. For example, Apple iOS
skipping to change at page 9, line 30 skipping to change at page 9, line 37
notifications towards the UA associated with the REGISTER request, or notifications towards the UA associated with the REGISTER request, or
perform any other procedures in this section. perform any other procedures in this section.
When the proxy receives a REGISTER request, if the REGISTER request When the proxy receives a REGISTER request, if the REGISTER request
contains a Feature-Caps header field with a 'sip.pns' feature- contains a Feature-Caps header field with a 'sip.pns' feature-
capability indicator, it indicates that an upstream proxy supports, capability indicator, it indicates that an upstream proxy supports,
and will request, push notifications towards the UA. The proxy MUST and will request, push notifications towards the UA. The proxy MUST
skip the rest of the procedures in this section, and process the skip the rest of the procedures in this section, and process the
REGISTER request using normal SIP procedures. REGISTER request using normal SIP procedures.
If the proxy considers the requested registration expiration interval
[RFC3261] to be too short, the proxy MUST either send a 423 (Interval
Too Brief) response to the REGISTER request or skip the rest of the
procedures in this section, and process the REGISTER request using
normal SIP procedures. Similarly, when the proxy receives a 2xx
response to the REGISTER request (see below), if the proxy considers
the registration expiration internal indicated by the registrar too
short, the proxy MUST NOT insert a Feature-Caps header field with a
'sip.pns' feature-capability indicator in the response, and the proxy
MUST NOT request push notifications associated with the registration.
A registration expiration interval MUST be considered too short if
the interval is smaller than the time prior to expiration that the
proxy would request a push notification. The proxy MAY consider the
interval too small based on its own policy so as to reduce load on
the system.
Otherwise, if the pn-provider SIP URI parameter identifies a PNS that Otherwise, if the pn-provider SIP URI parameter identifies a PNS that
the proxy does not support, or if the REGISTER request does not the proxy does not support, or if the REGISTER request does not
contain all additional information required for the specific PNS, the contain all additional information required for the specific PNS, the
proxy MUST either forward the request (e.g., if the proxy knows that proxy MUST either forward the request (e.g., if the proxy knows that
a downstream proxy supports the PNS) or send a SIP 555 (Push a downstream proxy supports the PNS) or send a SIP 555 (Push
Notification Service Not Supported) response to the REGISTER request. Notification Service Not Supported) response to the REGISTER request.
If the proxy sends a SIP 555 (Push Notification Service Not If the proxy sends a SIP 555 (Push Notification Service Not
Supported) response, the proxy SHOULD insert a Feature-Caps header Supported) response, the proxy SHOULD insert a Feature-Caps header
field with a 'sip.pns' feature-capability indicator in the response, field with a 'sip.pns' feature-capability indicator in the response,
identifying each PNS that the proxy supports. identifying each PNS that the proxy supports.
skipping to change at page 15, line 44 skipping to change at page 16, line 14
The value of the pn-param URI parameter is the Project ID. The value of the pn-param URI parameter is the Project ID.
The value of the pn-prid URI parameter is the Registration token, The value of the pn-prid URI parameter is the Registration token,
which is generated by the FCM SDK for each client app instance. which is generated by the FCM SDK for each client app instance.
For more information on the Project ID and Registration token: For more information on the Project ID and Registration token:
https://firebase.google.com/docs/cloud-messaging/concept-options https://firebase.google.com/docs/cloud-messaging/concept-options
11. Security Considerations 11. pn-provider, pn-param and pn-prid URI Parameters for RFC 8030
(Generic Event Delivery Using HTTP Push)
When Firebase Cloud Messaging (FCM) is used, the PNS related URI
parameters are set as described below.
The value of the pn-provider URI parameter is "webpush".
The value of the pn-param URI parameter is the push message
subscription resource URI.
The value of the pn-prid URI parameter is the push URI.
See RFC 8030 for more details:
https://tools.ietf.org/html/rfc8030
Note that encryption for web push [RFC8291] is not used, therefore
parameters for message encryption are not defined in this
specification. Web push permits the sending of a push message
without a payload without encryption.
12. Security Considerations
Different mechanisms exist for authenticating and authorizing devices Different mechanisms exist for authenticating and authorizing devices
and users registering with a PNS. The mechanisms for authorizing and and users registering with a PNS. The mechanisms for authorizing and
authenticating the users are PNS-specific, and are outside the scope authenticating the users are PNS-specific, and are outside the scope
of this document. In addition to the information that needs to be of this document. In addition to the information that needs to be
exchanged between a device and the PNS in order to establish a push exchanged between a device and the PNS in order to establish a push
notification subscription, the mechanism defined in this document notification subscription, the mechanism defined in this document
does not require any additional information to be exchanged between does not require any additional information to be exchanged between
the device and the PNS. the device and the PNS.
skipping to change at page 16, line 28 skipping to change at page 17, line 20
[RFC8292] defines a mechanism which allows a proxy to create a [RFC8292] defines a mechanism which allows a proxy to create a
identity itself to a PNS, by signing a JWT sent to the PNS using a identity itself to a PNS, by signing a JWT sent to the PNS using a
key pair. The public key serves as an identifier of the proxy, and key pair. The public key serves as an identifier of the proxy, and
can be used by devices to restrict push notifications to the proxy can be used by devices to restrict push notifications to the proxy
associated with the key. associated with the key.
The mechanism in this document does not require a proxy to include The mechanism in this document does not require a proxy to include
any payload (in addition to possible payload used for the PNS itself) any payload (in addition to possible payload used for the PNS itself)
when requesting push notifications. when requesting push notifications.
12. IANA considerations 13. IANA considerations
12.1. SIP URI Parameters 13.1. SIP URI Parameters
This section defines new SIP URI Parameters that extend the "SIP/SIPS This section defines new SIP URI Parameters that extend the "SIP/SIPS
URI Parameters" sub-registry [RFC3969] under the sip-parameters URI Parameters" sub-registry [RFC3969] under the sip-parameters
registry: http://www.iana.org/assignments/sip-parameters. registry: http://www.iana.org/assignments/sip-parameters.
12.1.1. pn-provider 13.1.1. pn-provider
Parameter Name: pn-provider Parameter Name: pn-provider
Predefined Values: No Predefined Values: No
Reference: RFC XXXX Reference: RFC XXXX
12.1.2. pn-param 13.1.2. pn-param
Parameter Name: pn-param Parameter Name: pn-param
Predefined Values: No Predefined Values: No
Reference: RFC XXXX Reference: RFC XXXX
12.1.3. pn-prid 13.1.3. pn-prid
Parameter Name: pn-prid Parameter Name: pn-prid
Predefined Values: No Predefined Values: No
Reference: RFC XXXX Reference: RFC XXXX
12.2. SIP Response Code 13.2. SIP Response Code
This section defines a new SIP response code that extends the This section defines a new SIP response code that extends the
"Response Codes" sub-registry [RFC3261] under the sip-parameters "Response Codes" sub-registry [RFC3261] under the sip-parameters
registry: http://www.iana.org/assignments/sip-parameters. registry: http://www.iana.org/assignments/sip-parameters.
Response Code Number: 555 Response Code Number: 555
Default Reason Phrase: Push Notification Service Not Supported Default Reason Phrase: Push Notification Service Not Supported
12.3. SIP Global Feature-Capability Indicator 13.3. SIP Global Feature-Capability Indicator
12.3.1. sip.pns 13.3.1. sip.pns
This section defines a new feature-capability indicator that extends This section defines a new feature-capability indicator that extends
the "SIP Feature-Capability Indicator Registration Tree" sub-registry the "SIP Feature-Capability Indicator Registration Tree" sub-registry
[RFC6809] under the sip-parameters registry: [RFC6809] under the sip-parameters registry:
http://www.iana.org/assignments/sip-parameters. http://www.iana.org/assignments/sip-parameters.
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 SIP REGISTER request or a SIP 2xx Feature-Caps header field of a SIP REGISTER request or a SIP 2xx
skipping to change at page 18, line 22 skipping to change at page 19, line 22
the indicator value. When included in a 555 (Push Notification the indicator value. When included in a 555 (Push Notification
Service Not Supported) response to a REGISTER request, the the Service Not Supported) response to a REGISTER request, the the
indicator indicates that the entity associated with the indicator indicates that the entity associated with the
indicator supports the SIP push mechanism, and the push indicator supports the SIP push mechanism, and the push
notification service(s) identified by the indicator value. notification service(s) identified by the indicator value.
Reference: [RFCXXXX] Reference: [RFCXXXX]
Contact: IESG (iesg@ietf.org) Contact: IESG (iesg@ietf.org)
12.3.2. sip.vapid 13.3.2. sip.vapid
This section defines a new feature-capability indicator that extends This section defines a new feature-capability indicator that extends
the "SIP Feature-Capability Indicator Registration Tree" sub-registry the "SIP Feature-Capability Indicator Registration Tree" sub-registry
[RFC6809] under the sip-parameters registry: [RFC6809] under the sip-parameters registry:
http://www.iana.org/assignments/sip-parameters. http://www.iana.org/assignments/sip-parameters.
Name: sip.vapid Name: sip.vapid
Description: This feature-capability indicator, when included in a Description: This feature-capability indicator, when included in a
SIP 2xx response to a SIP REGISTER request, indicates that the SIP 2xx response to a SIP REGISTER request, indicates that the
skipping to change at page 18, line 44 skipping to change at page 19, line 44
the Voluntary Application Server Identification (VAPID) the Voluntary Application Server Identification (VAPID)
mechanism when requesting push notifications towards the SIP UA mechanism when requesting push notifications towards the SIP UA
associated with the SIP registration. The indicator value is a associated with the SIP registration. The indicator value is a
public key identifying the entity, that can be used by a SIP UA public key identifying the entity, that can be used by a SIP UA
to restrict subscriptions to that entity. to restrict subscriptions to that entity.
Reference: [RFCXXXX] Reference: [RFCXXXX]
Contact: IESG (iesg@ietf.org) Contact: IESG (iesg@ietf.org)
12.3.3. sip.pnsreg 13.3.3. sip.pnsreg
This section defines a new feature-capability indicator that extends This section defines a new feature-capability indicator that extends
the "SIP Feature-Capability Indicator Registration Tree" sub-registry the "SIP Feature-Capability Indicator Registration Tree" sub-registry
[RFC6809] under the sip-parameters registry: [RFC6809] under the sip-parameters registry:
http://www.iana.org/assignments/sip-parameters. http://www.iana.org/assignments/sip-parameters.
Name: sip.pnsreg Name: sip.pnsreg
Description: This feature-capability indicator, when included in a Description: This feature-capability indicator, when included in a
skipping to change at page 19, line 25 skipping to change at page 20, line 25
the entity having to request push notifications towards the SIP the entity having to request push notifications towards the SIP
UA in order to trigger the REGISTER requests. The indicator UA in order to trigger the REGISTER requests. The indicator
value is the minimum value (given in seconds) before the value is the minimum value (given in seconds) before the
registration expireation when the entity expects to receive the registration expireation when the entity expects to receive the
REGISTER request. REGISTER request.
Reference: [RFCXXXX] Reference: [RFCXXXX]
Contact: IESG (iesg@ietf.org) Contact: IESG (iesg@ietf.org)
12.4. SIP Media Feature Tag 13.4. SIP Media Feature Tag
12.4.1. sip.pnsreg 13.4.1. sip.pnsreg
This section defines a new media feature tag that extends the "SIP This section defines a new media feature tag that extends the "SIP
Media Feature Tag Registration Tree" sub-registry [RFC3840] under the Media Feature Tag Registration Tree" sub-registry [RFC3840] under the
Media Feature Tag registry: https://www.iana.org/assignments/media- Media Feature Tag registry: https://www.iana.org/assignments/media-
feature-tags/media-feature-tags.xhtml. feature-tags/media-feature-tags.xhtml.
Media feature tag name: sip.pnsreg Media feature tag name: sip.pnsreg
Summary of the media feature indicated by this feature tag: This Summary of the media feature indicated by this feature tag: This
media feature tag, when included in the SIP Contact header media feature tag, when included in the SIP Contact header
skipping to change at page 20, line 26 skipping to change at page 21, line 26
Related standards or documents: [RFCXXXX] Related standards or documents: [RFCXXXX]
Security considerations: This media feature tag does not introduce Security considerations: This media feature tag does not introduce
new security considerations, as it simply indicates support for new security considerations, as it simply indicates support for
a basic SIP feature. If an attacker manages to remove the media a basic SIP feature. If an attacker manages to remove the media
feature tag, push notifications towards the client will be feature tag, push notifications towards the client will be
requested. requested.
Contact: IESG (iesg@ietf.org) Contact: IESG (iesg@ietf.org)
12.5. PNS Sub-registry Establishment 13.5. 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.
When a SIP URI pn-provider value is registered in the sub-registry, When a SIP URI pn-provider value is registered in the sub-registry,
it needs to meet the "Expert Review" policies defined in [RFC8126]. it needs to meet the "Expert Review" policies defined in [RFC8126].
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:
Value: The token under registration Value: The token under registration
Description: The name of the Push Notification Service (PNS) Description: The name of the Push Notification Service (PNS)
Document: A reference to the document defining the registration Document: A reference to the document defining the registration
This specification registers the following values: This specification registers the following values:
Value Description Document Value Description Document
------- ---------------------------------- ---------- ------- -------------------------------------- ----------
apns Apple Push Notification service [RFC XXXX] apns Apple Push Notification service [RFC XXXX]
fcm Firebase Cloud Messaging [RFC XXXX] fcm Firebase Cloud Messaging [RFC XXXX]
webpush Generic Event Delivery Using HTTP Push [RFC XXXX]
13. Acknowledgements 14. Acknowledgements
Thanks to Mickey Arnold, Paul Kyzivat, Dale Worley, Ranjit Avasarala, Thanks to Mickey Arnold, Paul Kyzivat, Dale Worley, Ranjit Avasarala,
Martin Thomson, Mikael Klein, Susanna Sjoholm, Kari-Pekka Perttula, Martin Thomson, Mikael Klein, Susanna Sjoholm, Kari-Pekka Perttula,
Liviu Chircu, Roman Shpount and Yehoshua Gev for reading the text, Liviu Chircu, Roman Shpount and Yehoshua Gev for reading the text,
and providing useful feedback. and providing useful feedback.
14. References 15. References
14.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, <https://www.rfc- DOI 10.17487/RFC3261, June 2002, <https://www.rfc-
skipping to change at page 22, line 21 skipping to change at page 23, line 21
[RFC8030] Thomson, M., Damaggio, E., and B. Raymor, Ed., "Generic [RFC8030] Thomson, M., Damaggio, E., and B. Raymor, Ed., "Generic
Event Delivery Using HTTP Push", RFC 8030, Event Delivery Using HTTP Push", RFC 8030,
DOI 10.17487/RFC8030, December 2016, <https://www.rfc- DOI 10.17487/RFC8030, December 2016, <https://www.rfc-
editor.org/info/rfc8030>. editor.org/info/rfc8030>.
[RFC8292] Thomson, M. and P. Beverloo, "Voluntary Application Server [RFC8292] Thomson, M. and P. Beverloo, "Voluntary Application Server
Identification (VAPID) for Web Push", RFC 8292, Identification (VAPID) for Web Push", RFC 8292,
DOI 10.17487/RFC8292, November 2017, <https://www.rfc- DOI 10.17487/RFC8292, November 2017, <https://www.rfc-
editor.org/info/rfc8292>. editor.org/info/rfc8292>.
14.2. Informative References 15.2. Informative References
[RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed., [RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed.,
"Managing Client-Initiated Connections in the Session "Managing Client-Initiated Connections in the Session
Initiation Protocol (SIP)", RFC 5626, Initiation Protocol (SIP)", RFC 5626,
DOI 10.17487/RFC5626, October 2009, <https://www.rfc- DOI 10.17487/RFC5626, October 2009, <https://www.rfc-
editor.org/info/rfc5626>. editor.org/info/rfc5626>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8291] Thomson, M., "Message Encryption for Web Push", RFC 8291,
DOI 10.17487/RFC8291, November 2017, <https://www.rfc-
editor.org/info/rfc8291>.
Authors' Addresses Authors' Addresses
Christer Holmberg Christer Holmberg
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: christer.holmberg@ericsson.com Email: christer.holmberg@ericsson.com
Michael Arnold Michael Arnold
Metaswitch Networks Metaswitch Networks
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield EN2 6BQ
United Kingdom United Kingdom
Email: Michael.Arnold@metaswitch.com Email: Michael.Arnold@metaswitch.com
 End of changes. 32 change blocks. 
51 lines changed or deleted 97 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/