Popular electronic mail systems include features allowing users to set up automated messages that are returned to message senders when the user is not able to deal with the message immediately. This feature is commonly known as "out-of-office" or "vacation" messages, because it is most commonly used when a user is unable to read their messages because they are out of the office (e.g., on vacation).
This document describes a similar system that enables XMPP users to setup out-of-office messages when they are away.
The basis for the e-mail system mechanism is considering an incoming message at the server level and determining whether to respond with a canned out-of-office message. While a system may send a response for each incoming message, many systems provide an optimization where a response to subsequent e-mail messages is sent after some period of time expires.
The requirements for this feature are fairly straightforward. A user MUST be able to:
All these requirements are satisfied by Personal Eventing Protocol (XEP-0163) , which is a subset of Publish-Subscribe (XEP-0060) .
The out-of-office setting contains a start-time, an end-time and a short message text.
The start and end times are informational only; i.e., the server does nothing with these values other than store them. PEP does not include node lifetime management (i.e., start and end times for the node); therefore, the server is unable to enforce any start and end times included in the settings.
Using the PEP mechanism a client creates out-of-office settings on a PEP node with the desired access model (such as Presence or Open). When a user (or their client) sends presence containing CAPS (see Entity Capabilities (XEP-0115) ) with an entry for out-of-office to a contact with an out-of-office message, the user's client is notified of the out-of-office message and may display, in a client-defined fashion, the out-of-office settings information.
Clients may rely on the PEP node for notifications of changes as well as automatic notification when the user logs-in (i.e., a user is notified of the current item on the out-of-office PEP node of another user on sending initial presence).
A user may request their current out-of-office message by sending an IQ get to the local server like so:
The <start/> and <end/> elements define the times between which this vacation message should be considered valid by a supporting client; the times are in the format specified by XMPP Date and Time Profiles (XEP-0082) .
The <message/> element contains the text of the message which the client may display for the user (when appropriate).
If the user has no stored vacation message, the user will receive a result like the following:
A user may set new vacation message by publishing a new item with an id of 'current' to the out-of-office node:
And by design, PEP sends a notification to all the user's resources.
The meaning of each element is as outlined above. All elements are required.
Additionally, the <start/> and <end/> elements MAY be empty (i.e., have no CDATA). When <start/> is empty, the client MUST take this to mean that the settings should take effect immediately. Similarly, when <end/> is empty, the client MUST take this to mean that the settings should never expire (unless they are explicitly removed).
A user may remove all stored vacation settings by sending an IQ to the local server like so:
TODO: Is the Delete And Notify functionality described in XEP-0060 18.104.22.168 widely implemented? If so, should that case be included here?
In PEP, a node's default access model is 'presence' (i.e., any other user with a subscription type "from" or "both" may subscribe to the node. PEP provides other access models including a 'whitelist.' See Publish-Subscribe (XEP-0060)  section 4.5 for a list of Node Access Models.
The whitelist access model can be used to hide the current out-of-office message. With an empty whitelist, no other users receive notification when the node changes. The client may also use this fact to allow the client's user to set up an out-of-office message before it becomes active.
PEP and PubSub allow for publishing an item and setting configuration on a node. A user may wish to create an initial, hidden out-of-office setting. They may do so by publishing an item with id='archive' and an access model of 'whitelist.' When the user enables the out-of-office settings, a configuration changing the access model to some other mode sends notifications as defined by PEP.
TODO: add an example of publishing an item and setting configuration with a single stanza i.e., find the appropriate example from Publish-Subscribe (XEP-0060)  or Personal Eventing Protocol (XEP-0163)  and include it here.
A server implementing out-of-office messages MUST implement Personal Eventing Protocol (XEP-0163) .
None yet defined.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) .
The 'urn:xmpp:ooo:0' namespace shall be registered with the XMPP Registrar  as a result of this document.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <firstname.lastname@example.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <email@example.com>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
6. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
7. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/