%ents; Support can be enabled via an external component or an internal server module/plugin. If claiming compliance using such an addition, the necessary components/modules/plugins MUST be detailed."> Support for the Entity Use Cases and Occupant Use Cases is REQUIRED; support for the remaining use cases is RECOMMENDED."> Only one of the recommended providers must be implemented for compliance."> Not required for command line or terminal based interfaces."> While 'User Avatars' is more modern, 'vCard-Based Avatars' is more widely deployed. Although it is suggested that to maximise interoperability with existing software a client fully supports both it is sufficient to claim compliance with this suite if the support for 'vCard-Based Avatars' is read-only."> While 'Personal Eventing Protocol' does not require all the features of 'Publish-Subscribe' to be available on the users' JIDs, and nor does this suite, it is desirable for this to be the case and it is expected that this will a requirement of future Compliance Suites."> ]>
XMPP Compliance Suites 2019 This document defines XMPP protocol compliance levels. &LEGALNOTICE; 0412 Draft 2019-02-29 Standards Track Standards RFC 6120 RFC 6121 RFC 7395 RFC 7590 RFC 7622 XEP-0030 XEP-0045 XEP-0048 XEP-0049 XEP-0084 XEP-0085 XEP-0114 XEP-0115 XEP-0124 XEP-0163 XEP-0191 XEP-0198 XEP-0206 XEP-0223 XEP-0249 XEP-0280 XEP-0313 XEP-0352 XEP-0368 XEP-0387 CS2019 Georg Lukas georg@op-co.de georg@yax.im 1.0.0 2019-04-04 XEP Editor Accepted as Draft per Council vote on 2019-03-27 0.5.0 2019-03-25 gl
  • Taken over ownership.
  • Improved structure of category and level names.
  • Added XEP-0313 and XEP-0410 to 'Advanced Group Chat'
 0.4.0 2019-01-13 jsc
  • Fix mess-up with TLS: TLS itself is of course required, it is just Direct TLS which is supposed to be advanced.
  • Add XEP-0308 (Last Message Correction) for Advanced Client
  • Minor typographical fixes
 0.2.0 2019-01-13 jsc
  • Remove XEP-0184 from server support (doesn't make sense)
  • Do not require Avatars for Core clients
  • Add a note for RFC 7622 and do not require it
  • Do not require XEP-0368 in core servers
 0.1.0 2018-12-16 XEP Editor (jsc) Accepted by vote of Council on 2018-12-19. 0.0.1 2018-12-08 jsc

First draft based on XEP-0378. Non-editorial Changes:

  • Prefer XEP-0084 for Avatars, use XEP-0398 for compat.
  • Add XEP-0184

The &XSF; defines protocol suites for the purpose of compliance testing and software certification. This document specifies compliance levels for XMPP clients and servers; it is hoped that this document will advance the state of the art, and provide guidance and eventual certification to XMPP client and server authors.

This document defines Categories based on typical use cases (Core, Web, IM, Mobile) and Levels (Core, Advanced) based on functionality in the respective category.

Unless explicitly noted, support for the listed specifications is REQUIRED for compliance purposes. A feature is considered supported if all comma separated feature providers listed in the "Providers" column are implemented (unless otherwise noted).

Feature Core Server Core Client Advanced Server Advanced Client Providers
Core features ✓ ✓ ✓ ✓ &rfc6120; &rfc7622; is not listed due to the unclear interoperability impact of using PRECIS and Stringprep in the same ecosystem.
TLS ✓ ✓ ✓ ✓ &rfc7590;
Direct TLS ✕ ✕ ✓Server support of XEP-0368 means having the ability to accept direct TLS connections. ✓ &xep0368;
Feature discovery ✓ ✓ ✓ ✓ &xep0030;
Feature broadcasts ✕ ✓ ✓ ✓ &xep0115;
Server Extensibility ✓ N/A ✓ N/A &xep0114;
Event publishing ✕ ✕ ✓&pubsubjid; ✓ &xep0163;

To be considered XMPP web compliant, all features from the core compliance category must be met, as well as all features in this suite.

Feature Core Server Core Client Advanced Server Advanced Client Providers
Web Connection Mechanisms ✓&component; ✓&onlyone; ✓&component; ✓&onlyone; &rfc7395;, &xep0206; (See also: &xep0124;)

To be considered XMPP IM compliant, all features from the core compliance category must be met, as well as all features in this suite.

Feature Core Server Core Client Advanced Server Advanced Client Providers
Core features ✓ ✓ ✓ ✓ &rfc6121;
User Avatars N/A ✕ N/A ✓&nocli; &xep0084;
User Avatar Compatibility ✕ ✕ ✓ ✓&nocli; &xep0398;, &xep0153;
vcard-temp ✓ ✓ ✓ ✓ &xep0054;
Outbound Message Synchronization ✓ ✓ ✓ ✓ &xep0280;
User Blocking ✕ ✕ ✓ ✓ &xep0191;
Group Chat ✓&component; ✓&usecases; ✓&component; ✓&usecases; &xep0045;Implementations should take note that future versions of these compliance suites may rely on &xep0369; instead., &xep0249;
Advanced Group Chat ✕ ✕ ✓&component; ✓ &xep0048;, &xep0313;Support for requesting history from a MUC archive as opposed to from the user's account., &xep0410;
Persistent Storage of Private Data via PubSub ✕ ✕ ✓&component; ✓ &xep0223;
Private XML Storage ✕ ✕ ✓&component; ✓ &xep0049;
Session Resumption ✕ ✕ ✓ ✓ &xep0198;
Stanza Acknowledgements ✕ ✕ ✓ ✓ &xep0198;
Message Acknowledgements N/A ✕ N/A ✓ &xep0184;
History Storage / Retrieval ✕ ✕ ✓ ✓ &xep0313;
Chat States N/A ✕ N/A ✓ &xep0085;
Message Correction N/A ✕ N/A ✓ &xep0308;

To be considered XMPP mobile compliant, all features from the core compliance category must be met, as well as all features in this suite.

Feature Core Server Core Client Advanced Server Advanced Client Providers
Session Resumption ✓ ✓ ✓ ✓ &xep0198;
Stanza Acknowledgements ✓ ✓ ✓ ✓ &xep0198;
Client State Indication ✓ ✓ ✓ ✓ &xep0352;
Third Party Push Notifications ✕ ✕ ✓&component; ✓ &xep0357;

Some of the protocol specifications referenced herein have their own dependencies; developers need to consult the relevant specifications for further information.

This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.

This document requires no interaction with &IANA;.

This document requires no interaction with the ®ISTRAR;.

The author would like to thank Guus der Kinderen, Dele Olajide, Marc Laporte, Dave Cridland, Daniel Gultsch, Florian Schmaus, Tobias Markmann, and Jonas Schäfer for their suggestions.