diff --git a/xep-0318.xml b/xep-0318.xml index 648201b4..37e42170 100644 --- a/xep-0318.xml +++ b/xep-0318.xml @@ -6,8 +6,8 @@
- Last Presence using Delayed Delivery - This specification defines a way to determine the time when a XMPP entity has last changed its presence. + Best Practices for Client Initiated Presence Probes + This specification defines a way to determine the time when a XMPP entity has last changed its presence. Using client initiated presence probes the current presence of subscribed XMPP users can be requested. In addition a protocol to request the uptime of servers and components is defined herein. &LEGALNOTICE; 0318 Experimental @@ -24,6 +24,12 @@ last-presence &tobias; + + 0.2 + 2013-08-06 + tobias +

Fix issues raised in XMPP Council meeting.

 + 0.1 2013-03-04 @@ -38,35 +44,52 @@
-

This protocol describes a way to communicate time of last presence change with other XMPP entities over presence stanzas. This is done extending presence stanzas with delayed delivery information according to &xep0203; and can be used to determine the time of last presence change for XMPP entities includeing servers. For users on the same server, the server also adds delyed delivery information to the presence responses.

-

The time of the delayed delivery information attatched to the presence indicates the time a XMPP entity has last changed to this presence.

+

&rfc6121;, section 4.3, defines presence probes as a way for servers to actively ping for presence status of XMPP contacts. In some scenarios however, clients want to request an update on the status of a XMPP contact.

+ + +

While &rfc6121; specifically advises against (SHOULD NOT) clients sending presence probes to XMPP contacts, there are valid scenarios where XMPP clients want to send presence probes.

+

According to &rfc6121;, contacts a client doesn't have presence information on, are expected to be offline and server aren't mandated to explicitly send offline presence to the client for offline users.

+

In addition, clients in constrained environments (i.e. mobile clients), could explicitly tell the server to filter out presence stanzas of certain kind, to keep communication to a minimum. One such protocol is &xep0273;.

+

This causes presence information to be outdated and any information, that might have been attached to the offline presence, i.e. &xep0203;, to be missing at client side.

+

Sending presence probes from the client should be based on human request, i.e. opening a chat dialog to an offline contact when messing full presence information for that contact. Clients MUST NOT send presence probes to all contacts that they think are offline after login.

 - -

This section describes how to determine the time a user when offline or, in general, changed to her current presence state. This is merly a description since the protocol is already described in &rfc6121;, section 4.3.2.

-

The following example show a possible incoming presence in response to going online by sending your own available presence.

- - +This section describes two major use cases of the described protocol, client initiated presence probes. + +

In some situations, after login, the client has incomplete presence information for offline contacts. The user might be interested in status text of the offline presence of a contact or when a contact went offline. This information can be requested, i.e. when the user opens a chat dialog to an offline user, using a client initiated presence probe and is described in the following two examples.

+

Initialilly a client requests the current presence information of a contact by sending out a presence probe.

+]]> +

The other side's server, in this example montague.com, then responds with the last known presence of the user, including &xep0203; and other information provided by the user.

+ + Going offline. Out of battery. + ]]> - - -

Reqesting the uptime of a server or component is done by sending a directed presence probe to the XMPP entity of interest. The request is shown in the following example.

- + +

XMPP servers typically don't have all the properties known from XMPP clients, like presence or rosters. However, &xep0267; for example added rosters to XMPP servers.

+

In a similar manner, this extension describes the use of presence for XMPP servers and XMPP components. Basically, when a XMPP server or component starts up it's expected to set its presence to online.

+

With this concept, any party could easily request the time a XMPP server or component went online, by sending a presence probe to it.

+]]> -

The server or component then responds with an available presence, extended with delayed delivery information, according to XEP-0203, indicating its startup time. This is shown below:

- - + ]]> - +

Thanks to Kim Alvefur and Lance Stout for their helpful comments.

 -

Adding delayed delivery notation to the presence probe responses exposes information a user might not expect to have exposed. However the information about last presence change is known to all entities subscribed to one's presence which are online. This extension just provides this information to XMPP entities which have been offline during the course of presence change.

-

It's worth to note that the security considerations of &xep0082; apply here.

+

Adding delayed delivery notation to the presence probe responses exposes information a user might not expect to have exposed. However, the information about last presence change is known to all entities subscribed to one's presence which are online. This extension just provides this information to XMPP entities which have been offline during the course of presence change.

+

The security considerations of &xep0082; apply here.

This document requires no interaction with &IANA;.