WARNING: This document has been obsoleted by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality are advised to implement the protocol that supersedes this one (if any).
When one has multiple clients at different locations logged in
simultaneously, it is often desirable to control these clients from
the client you are currently using. There are a number of common tasks
one might want to perform remotely on clients: change the status of the
client, forward all received unread messages to this client, and so on.
Therefore, it makes sense to define a protocol for performing these tasks.
This document describes a protocol to perform a set of common tasks on a
remote client, by specifying a profile of Ad-Hoc Commands (XEP-0050) .
It is common to forget changing the status of a resource when leaving the
client for a longer period. When realizing this while at another location, it
might be desirable to change the status from there, to avoid contacts
thinking that resource is attended and sending it messages.
Unless an error occurs (see the
Error Handling section below), the service
SHOULD return the appropriate form.
If the 'status-priority' variable is omitted, the client SHOULD NOT
change the priority of the client
Notification of completion MAY include the processed data in a data
form of type 'result'.
4.2 Forward Unread Messages Residing at a Remote Client¶
A user might want to forward all the unread messages residing at the
remote client to the local client (e.g. when the remote client was
accidentally left on-line, and has received messages in the meantime).
For example, suppose Romeo sends a message to Juliet, thinking she is
still on her balcony.
The balcony client receives the message:
However, Juliet is in her chamber, so she doesn't know about the message
Realizing she left her balcony client unattended, she sends a request to
the remote client to forward all unread messages.
The client forwards all unread messages to the local client, adding
information about the origin of the message (using the 'ofrom' Extended Stanza Addressing (XEP-0033) 
address, and the Delayed Delivery (XEP-0203)  timestamp of the original message).
The chamber client receives both these messages and a confirmation that
the command was completed.
A client MAY provide a more fine-grained implementation, e.g. by
presenting the requester an extra form to select which messages have to
It might be desirable to remotely set some run-time options of a client.
For example, when neighbours complain about the sounds your client makes
while you're at another location, you could turn the sounds off at the
Unless an error occurs (see the Error
Handling section below), the service SHOULD return the
The remote client sets the values of the options to their requested
If a variable is omitted, the client SHOULD NOT change the value of the
Notification of completion MAY include the processed data in a data form
of type 'result'.
Several error conditions are possible when an entity sends a command
request to the service, as defined in the following table. If one of these
errors occurs, the service MUST return an error stanza to the requesting
Implementations of this protocol MAY add or remove fields to forms as
they see fit. For example, when setting the status of a remote client that
supports multiple accounts, the client may choose to add a boolean field
to allow the user to specify whether the status change should be applied
globally or only to the receiving account.
Implementations MAY also introduce extra forms for commands. For example,
when forwarding unread messages, a client could return a form containing a
of short descriptions of unread messages, allowing the user to select the
messages he wants to forward.
The ability to complete the tasks specified herein MUST NOT be granted
to users who lack privileges to control a client. A sensible
access policy is to only allow remote controlling by other
resources of the same account used by the client. If other accounts
are to be able to remote control the client, the client needs more
complex access right management.
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.
Disclaimer of Warranty
## 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. ##
Limitation of Liability
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 HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.
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 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".
7. 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/>.