There are a variety of reasons why a user may wish to change their JID. For example, a surname change because of marriage or simply an easier JID to remember.
This XEP defines an approach for communicating that your JID has moved to a new JID, extending the existing subscription protocol documented in XMPP IM . The steps outlined here may be done either through a client or automated by a server.
In this scenario firstname.lastname@example.org moves to email@example.com. Both the firstname.lastname@example.org and email@example.com accounts have been created and still exist. The roster for firstname.lastname@example.org is empty and the user wants to populate it with their entries from email@example.com.
Because the original JID is no longer going to be used, the user SHOULD unsubscribe from all the outbound subscriptions firstname.lastname@example.org had. These can be identified as those in the 'to' or 'ask' states as defined in the 'jabber:iq:roster' protocol in RFC 6121.
To unsubscribe all outbound subscriptions for the original JID send an unsubscribe <presence/> stanza to all the old contacts with a <moved/> element containing the new JID.
There is the potential for other users to send a malicious unsubscribe containing a spoofed <moved/> JID. Therefore, clients SHOULD NOT automatically subscribe to the JID contained in the <moved/> stanza when receiving a subscribe <presence/> stanza without displaying the <moved/> JID to the user. See the Security Considerations section for details.
Because the original JID is no longer going to be used, the user SHOULD unsubscribe from all contacts the email@example.com had an inbound subscription from. These can be identified as those in the 'from' subscription state as defined in in the 'jabber:iq:roster' protocol in RFC 6121.
To unsubscribe all inbound subscriptions send an unsubscribed <presence/> stanza to all the old contacts with a <moved/> element containing the new JID.
There is the potential for other users to send a malicious unsubscribed containing a spoofed <moved/> JID. Therefore, clients SHOULD NOT automatically subscribe to the JID contained in the <moved/> stanza without displaying the <moved/> JID to the user. See the Security Considerations section for details.
Once the new JID has been created on a server it is possible for the new JID to subscribe to the contacts they had on the original JID's roster. This is done by sending a new subscription request with a <moved/> element containing the new JID.
The new subscription MUST come from the new JID's server.
There is the potential for other users to send a malicious subscribe request and spoof the content of the <moved/> element identifying an original JID. Therefore, clients SHOULD NOT automatically unsubscribe an existing roster entry if is listed as the target in the <moved/> element when a subscribe is received. See the Security Consideration section for details.
Clients accepting the moved subscription SHOULD indicate to the user that that this subscription request was the result of a move operation and because of potential malicious behavior SHOULD NOT auto-accept the subscription without displaying the <moved/> JID to the user.
RFC 6120 clarifies that an incoming subscribe <presence/> stanza MUST be preserved by the server and <presence/> stanzas of type unsubscribe and unsubscribed are not preserved on the server. Therefore, for a contact who is offline, their servers MAY have automatically removed the original roster entry when seeing the unsubscribe and unsubscribed stanzas. At the time of writing this XEP, NOT saving and forwarding the presence stanzas will be the default behavior of most servers.
What this means is that a contact coming online after the rename outlined above MAY only see the <presence/> of type 'subscribe' with the <moved/> element. Clients should be aware of this behavior.
In following the principle of least surprise, it is considered good practice to send the subscribe stanza after the unsubscribe and unsubscribed stanzas.
One of the side effects of this scheme is the potential for a contact to lose the groups to which it had organized the original JID. Clients aware of the <moved/> element can mitigate this with the following rules.
As discussed in 'Contacts Offline at the Time the Rename Occurs', a server MAY automatically handle the unsubscribe and unsubscribed stanzas. If this occurs it will be impossible to preserve the original groups.
If the original JID, firstname.lastname@example.org, had only an inbound subscription (from or pending in), then the contact will only receive an unsubscribed <presence/> stanza. The contact's client, knowing the state of the subscription (which is 'to' or 'none' with 'ask='subscribe' from the contact's perspective), at that point MAY choose to prompt the user to subscribe to the new JID listed in the <moved/> element.
Because of the ability to spoof the <moved/> element, the client SHOULD NOT automatically subscribe to the <moved/> element target, but SHOULD present the new JID to the contact before sending out a subscription request.
If the original JID, email@example.com, had only an outbound subscription (to or ask), then the contact SHOULD only receive an unsubscribe <presence/> stanza. The contact's client, knowing the state of the subscription (which is 'from' from the contact's perspective), at that point MAY choose to prompt the user to subscribe to the new JID listed in the <moved/> element.
Because of the ability to spoof the <moved/> element, the client SHOULD NOT automatically subscribe to the <moved/> element target.
|Server state||Client state (jabber:iq:roster)||Send unsubscribe from original JID||Send unsubscribed from original JID||Send subscribe from new JID|
|none + pending out||none + ask='subscribe'||yes||yes|
|none + pending in||n/a||yes - server only|
|none + pending in/out||none + ask='subscribe'||yes||yes - server only||yes|
|to + pending in||to||yes||yes - server only||yes|
|from + pending out||from/none + ask='subscribe'||yes||yes||yes|
It is not intended for servers to strip any <moved/> elements from <presence/> stanzas sent in from a client. This allows clients as well as servers to implement these same procedures.
In order to prevent other users from maliciously altering contacts the client SHOULD NOT automatically subscribe to a <moved/> JID when it receives an unsubscribe and SHOULD NOT automatically unsubscribe to a <moved/> JID when it receives a subscribe.
The following illustrates an example malicious attack.
A similar attack can be done with a new subscribe request causing users by guessing which users are subscribed to a contact.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) .
This specification defines the following XML namespace:
Upon advancement of this specification from a status of Experimental to a status of Draft, the XMPP Registrar  shall add the foregoing namespace to the registry located at <https://xmpp.org/registrar/namespaces.html>, as described in Section 4 of XMPP Registrar Function (XEP-0053) .
If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.
The author wishes to thank Doug Abbink, Mikhail Belov, Peter Saint-Andre, and Peter Sheu for their feedback.
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".
3. 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/>.
4. 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/
Fix trivial typo
Initial published version.
Modified syntax to use 'old' and 'new' attributes.
Added one-way subscription section
Change MUST NOT to SHOULD NOT for clients auto-subscribing back; differentiate between inbound and outbound subscriptions.
Add one-way subscription comments.