diff --git a/xep-0357.xml b/xep-0357.xml index 73a1f6df..9a4b95d2 100644 --- a/xep-0357.xml +++ b/xep-0357.xml @@ -6,7 +6,7 @@
- Push + Push Notifications This specification defines a way for an XMPP servers to deliver information for use in push notifications to mobile and other devices. &LEGALNOTICE; 0357 @@ -29,6 +29,12 @@ lancestout@gmail.com lance@lance.im + + 0.2 + 2015-09-10 + lance +

Change the name to 'Push Notifications' based on feedback.

 + 0.1 2015-03-18 @@ -52,7 +58,7 @@

The purpose of push notifications is to inform users of new messages or other pertinent information even when they have no XMPP clients online.

Typically, these notifications are delivered to a user's mobile device, displaying a notice that can trigger opening an XMPP client to continue a conversation or answer a Jingle session request.

-

There have been several push noticiations implementations by mobile XMPP client vendors. However, experience has shown that these implementations carried several drawbacks:

+

There have been several push notification implementations by mobile XMPP client vendors. However, experience has shown that these implementations carried several drawbacks:

  • Treated the XMPP client and XMPP server as one unified service, such that push notifications only worked using the "official" client.
  • Proxied a user's session through the client provider's backend services in order to monitor for and trigger push notifications.
    • @@ -76,7 +82,7 @@
  • The third-party (and potentially proprietary or platform-dependent) push service delivers the notification from the client application's backend service to the user's device.
    • -

    This two-tiered push architecture allows the user's XMPP server to deliver notifications to arbitrary third-pary clients, and in turn allows those clients to use the appropriate delivery mechanism for their platforms without having to share any private keys or other credentials with the XMPP server.

    +

    This two-tiered push architecture allows the user's XMPP server to deliver notifications to arbitrary third-party clients, and in turn allows those clients to use the appropriate delivery mechanism for their platforms without having to share any private keys or other credentials with the XMPP server.

    The current state-of-the-art for a generic push notification service requires four actors:

    @@ -335,7 +341,7 @@

    If additional data was provided when enabling the service, the publish request SHOULD include the data as publish options.

    - Customizable Message Routing (XEP-0354) XEP-0354: Customizable Message Routing <http://xmpp.org/extensions/xep-0354.html>." > Namespace Delegation (XEP-0355) XEP-0355: Namespace Delegation <http://xmpp.org/extensions/xep-0355.html>." > Privileged Entity (XEP-0356) XEP-0356: Privileged Entity <http://xmpp.org/extensions/xep-0356.html>." > -Push (XEP-0357) XEP-0357: Push <http://xmpp.org/extensions/xep-0357.html>." > +Push Notifications (XEP-0357) XEP-0357: Push Notifications <http://xmpp.org/extensions/xep-0357.html>." > Publishing Available Jingle Sessions (XEP-0358) XEP-0358: Publishing Available Jingle Sessions <http://xmpp.org/extensions/xep-0358.html>." > Unique and Stable Stanza IDs (XEP-0359) XEP-0359: Unique and Stable Stanza IDs <http://xmpp.org/extensions/xep-0359.html>." > Nonzas (are not Stanzas) (XEP-0360) XEP-0360: Nonzas (are not Stanzas) <http://xmpp.org/extensions/xep-0360.html>." >