%ents; Support can be enabled via an external component or an internal server module/plugin."> 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."> ]>
XMPP Compliance Suites 2018 This document defines XMPP protocol compliance levels. &LEGALNOTICE; 0387 Proposed 2017-12-21 2017-11-15 Standards Track Standards RFC 6120 RFC 6121 RFC 7395 RFC 7590 RFC 7622 XEP-0030 XEP-0045 XEP-0084 XEP-0085 XEP-0114 XEP-0115 XEP-0124 XEP-0163 XEP-0191 XEP-0198 XEP-0206 XEP-0249 XEP-0280 XEP-0313 XEP-0352 XEP-0368 XEP-0375 CS2018 &sam; &jonaswielicki; 0.3.3 2018-01-23 XEP Editor (jwi)

Add Jonas as author.

Move back to experimental.

 0.3.2 2018-01-18 XEP Editor (ssw, revision added by jwi)

Rejected by council

 0.3.1 2017-11-04 ssw

Update RFC 6122 references to RFC 7622

 0.3.0 2017-11-01 ssw

Bump year to 2018

 0.2.0 2017-02-10 ssw
  • Add XEP-0085: Chat State Notifications
  • Add XEP-0249: Direct MUC Invitations
  • Add XEP-0368: SRV records for XMPP over TLS
  • Typo fixes (thanks to Georg Lucas)
 0.1.0 2017-02-08 ssw

First draft updated from XEP-0375 accepted by the council.

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. 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;
TLS ✓ ✓ ✓ ✓ &rfc7590;, &xep0368;Server support means having the ability to accept direct TLS connections.
Feature discovery ✓ ✓ ✓ ✓ &xep0030;
Feature broadcasts ✕ ✓ ✓ ✓ &xep0115;
Server Extensibility ✓ N/A ✓ N/A &xep0114;
Event publishing ✕ ✕ ✓ ✓ &xep0163;

To be considered XMPP web compliant, all features from the core compliance suite 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 suite 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 ✓&nocli; N/A ✓&nocli; &xep0084;
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;
Bookmarks ✕ ✕ ✓&component; ✓ &xep0048;
Session Resumption ✕ ✕ ✓ ✓ &xep0198;
Stanza Acknowledgements ✕ ✕ ✓ ✓ &xep0198;
History Storage / Retrieval ✕ ✕ ✓ ✓ &xep0313;
Chat States N/A ✕ N/A ✓ &xep0085;

To be considered XMPP mobile compliant, all features from the core compliance suite 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 Indiciation ✓ ✓ ✓ ✓ &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 Georg Lukas for their suggestions.