XMPP 2.0
This page summarizes a few ideas on things which could/should/may be in an eventual XMPP 2.0.
This page is a draft written by individuals who may or may not be XSF members. It does not necessarily reflect the view or intention of XSF Board, Council or the XSF as organization as a whole, if that’s a thing.
Issues existing in XMPP 1.0
Routing rules
Current situation
The routing rules for stanzas addressed to the bare JID in XMPP 1.0 are blurry and don’t really match modern always-online but not necessarily in the view of the user multi-device use cases. This is why Message Carbons (XEP-0280) have been invented. They allow a device to tell the server that it wants to receive carbon-copies of all messages received by any resource of an account. This only affects <message/> stanzas (for presence, there is a well-defined broadcast-to-all-resources mechanism and IQs can only be addressed to a single resource).
However, throughout the history of XMPP, there have been XEPs which use messages to send data which is really only of interest for a single resource. Prime examples are In-Band Bytestreams (XEP-0047), privacy enhancing protocols such as the (in)famous OTR and (private messages from) Multi-User Chat (XEP-0045). This lead to Message Carbon rules being hand-wavy and blurry, some of the behaviour being implementation-defined, depending on co-operating clients which do not speak Message Carbons themselves and other unfortunaties.
Proposed change
To make things simpler, routing rules (for messages) could be re-defined to the following:
- If a message is addressed to a bare account JID, it is delivered to all online resources of the JID.
- If a message is addressed to a full JID:
- if an online resource exists at that full JID, the message is delivered to that resource
- if no online resource exists, an error is returned (NOTE: privacy implications and possible resource scanning need to be thought through)
In addition, resource locking as described in RFC 6121 would be discouraged and deprecated, since it interferes with these rules. See below for considerations on resource locking.
Migration path in a hypothetical XMPP 2.0 Session
The server(s) would translate the semantics for non-XMPP-2.0 servers and clients. For this, the following transformations would be applied when talking to non-XMPP-2.0 nodes:
- If a message is addressed to a full JID, a
<private/>(see Avoiding Carbons for a single message) or a<no-copy/>hint is injected.
Resource locking
Current situation
RFC 6121, Section 5.1 describes the process of resource locking for one-on-one chats. In essence, once a response is received from a peer resource, following messages are sent to that resource.
The intent was that messages would always arrive at the device currently used by the conversation partner (since Message Carbons were not there), since the routing rules for message stanzas did not enforce that behaviour.
Proposed change
Eliminate resource locking entirely. Instead, always send conversational content to the bare JID.
Migration path in a hypothetical XMPP 2.0 Session
None.