%ents; ]>
XMPP Compliance Suites 2012 This document defines XMPP protocol compliance levels for 2012. &LEGALNOTICE; 0302 Obsolete Standards Track Standards RFC 6120 RFC 6121 RFC 6122 XEP-0030 XEP-0045 XEP-0054 XEP-0085 XEP-0114 XEP-0115 XEP-0124 XEP-0163 XEP-0184 XEP-0191 XEP-0198 XEP-0206 XEP-0270 XEP-0375 N/A &stpeter; 0.1 2011-07-21 psa

Initial published version.

 0.0.2 2011-07-17 psa

Added RFC 6122, XEP-0184, and XEP-0198.

 0.0.1 2011-07-06 psa

Rough draft, copied and modified from XEP-0270.

The &XSF; defines protocol suites for the purpose of compliance testing and software certification. This document specifies the 2012 compliance levels for XMPP clients and servers. The XSF neglected to publish compliance suites for 2011; therefore the predecessor to this document is &xep0270;. Unless qualified where explicitly noted, support for the listed specifications is REQUIRED for compliance purposes.
Spec Core Server Core Client Advanced Server Advanced Client
&rfc6120; ✓ ✓ ✓ ✓
&rfc6121; ✓ ✓ ✓ ✓
&rfc6122; ✓ ✓ ✓ ✓
&xep0030; ✓ ✓ ✓ ✓
&xep0115; ✕ ✓ ✓ * ✓
&xep0114; ✓ N/A ✓ N/A
&xep0191; ✕ ✕ ✓ ✕
&xep0124; ✕ ✕ ✓ ** ✕
&xep0206; ✕ ✕ ✓ ** ✕
&xep0054; ✕ ✕ ✓ ✓
&xep0163; ✕ ✕ ✓ ✓
&xep0045; ✕ ✕ ✓ ** ✓ ***
&xep0085; N/A ✕ N/A ✓
&xep0184; N/A ✕ N/A ✓
&xep0198; ✕ ✕ ✓ ✓

* Necessary to support Personal Eventing Protocol (PEP).

** 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.

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

Developers are advised to refer to &xep0178; regarding proper implementation of the SASL EXTERNAL mechanism in XMPP.

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;.

Thanks to Dave Cridland, Waqas Hussain, Kevin Smith, and Matthew Wild for their feedback.