You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

344 lines
12 KiB

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
<!ENTITY component "<note>Support can be enabled via an external component or an internal server module/plugin.</note>">
<!ENTITY usecases "<note>Support for the Entity Use Cases and Occupant Use Cases is REQUIRED; support for the remaining use cases is RECOMMENDED.</note>">
<!ENTITY onlyone "<note>Only one of the recommended providers must be implemented for compliance.</note>">
<!ENTITY nocli "<note>Not required for command line or terminal based interfaces.</note>">
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>XMPP Compliance Suites 2017</title>
<abstract>
This document defines XMPP protocol compliance levels for 2017.
</abstract>
&LEGALNOTICE;
<number>0387</number>
<status>Proposed</status>
<lastcall>2017-10-30</lastcall>
<type>Standards Track</type>
<sig>Standards</sig>
<dependencies>
<spec>RFC 6120</spec>
<spec>RFC 6121</spec>
<spec>RFC 6122</spec>
<spec>RFC 7395</spec>
<spec>RFC 7590</spec>
<spec>XEP-0030</spec>
<spec>XEP-0045</spec>
<spec>XEP-0084</spec>
<spec>XEP-0085</spec>
<spec>XEP-0114</spec>
<spec>XEP-0115</spec>
<spec>XEP-0124</spec>
<spec>XEP-0163</spec>
<spec>XEP-0191</spec>
<spec>XEP-0198</spec>
<spec>XEP-0206</spec>
<spec>XEP-0249</spec>
<spec>XEP-0280</spec>
<spec>XEP-0313</spec>
<spec>XEP-0352</spec>
<spec>XEP-0368</spec>
</dependencies>
<supersedes>
<spec>XEP-0375</spec>
</supersedes>
<supersededby/>
<shortname>CS2017</shortname>
&sam;
<revision>
<version>0.2.0</version>
<date>2017-02-10</date>
<initials>ssw</initials>
<remark>
<ul>
<li>Add XEP-0085: Chat State Notifications</li>
<li>Add XEP-0249: Direct MUC Invitations</li>
<li>Add XEP-0368: SRV records for XMPP over TLS</li>
<li>Typo fixes (thanks to Georg Lucas)</li>
</ul>
</remark>
</revision>
<revision>
<version>0.1.0</version>
<date>2017-02-08</date>
<initials>ssw</initials>
<remark>
<p>First draft updated from XEP-0375 accepted by the council.</p>
</remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>
The &XSF; defines protocol suites for the purpose of compliance testing
and software certification.
This document specifies the 2017 compliance levels for XMPP clients and
servers; it is hoped that this document will advance the state of the art,
and provide guidence 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).
</p>
</section1>
<section1 topic='Compliance Levels' anchor='levels'>
<section2 topic='Core Compliance Suite' anchor='core'>
<table caption='XMPP Core Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Core features</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&rfc6120;, &rfc6122;</td>
</tr>
<tr>
<td><strong>TLS</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&rfc7590;, &xep0368;<note>Server support means having the ability to accept direct TLS connections.</note></td>
</tr>
<tr>
<td><strong>Feature discovery</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0030;</td>
</tr>
<tr>
<td><strong>Feature broadcasts</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0115;</td>
</tr>
<tr>
<td><strong>Server Extensibility</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;</td>
<td align='center'>N/A</td>
<td>&xep0114;</td>
</tr>
<tr>
<td><strong>Event publishing</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0163;</td>
</tr>
</table>
</section2>
<section2 topic='Web Compliance Suite' anchor='web'>
<p>
To be considered XMPP web compliant, all features from the core
compliance suite must be met, as well as all features in this suite.
</p>
<table caption='XMPP Web Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Web Connection Mechanisms</strong></td>
<td align='center'>&#10003;&component;</td>
<td align='center'>&#10003;&onlyone;</td>
<td align='center'>&#10003;&component;</td>
<td align='center'>&#10003;&onlyone;</td>
<td>&rfc7395;, &xep0206; (See also: &xep0124;)</td>
</tr>
</table>
</section2>
<section2 topic='IM Compliance Suite' anchor='im'>
<p>
To be considered XMPP IM compliant, all features from the core
compliance suite must be met, as well as all features in this suite.
</p>
<table caption='XMPP IM Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Core features</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&rfc6121;</td>
</tr>
<tr>
<td><strong>User Avatars</strong></td>
<td align='center'>N/A</td>
<td align='center'>&#10003;&nocli;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;&nocli;</td>
<td>&xep0084;</td>
</tr>
<tr>
<td><strong>Outbound Message Synchronization</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0280;</td>
</tr>
<tr>
<td><strong>User Blocking</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0191;</td>
</tr>
<tr>
<td><strong>Group Chat</strong></td>
<td align='center'>&#10003;&component;</td>
<td align='center'>&#10003;&usecases;</td>
<td align='center'>&#10003;&component;</td>
<td align='center'>&#10003;&usecases;</td>
<td>&xep0045;<note>Implementations should take note that future versions of these compliance suites may rely on &xep0369; instead.</note>, &xep0249;</td>
</tr>
<tr>
<td><strong>Bookmarks</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;&component;</td>
<td align='center'>&#10003;</td>
<td>&xep0048;</td>
</tr>
<tr>
<td><strong>Session Resumption</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>Stanza Acknowledgements</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>History Storage / Retrieval</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0313;</td>
</tr>
<tr>
<td><strong>Chat States</strong></td>
<td align='center'>N/A</td>
<td align='center'>&#10005;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;</td>
<td>&xep0085;</td>
</tr>
</table>
</section2>
<section2 topic='Mobile Compliance Suite' anchor='mobile'>
<p>
To be considered XMPP mobile compliant, all features from the core
compliance suite must be met, as well as all features in this suite.
</p>
<table caption='XMPP Mobile Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Session Resumption</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>Stanza Acknowledgements</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>Client State Indiciation</strong></td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td>&xep0352;</td>
</tr>
<tr>
<td><strong>Third Party Push Notifications</strong></td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;&component;</td>
<td align='center'>&#10003;</td>
<td>&xep0357;</td>
</tr>
</table>
</section2>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
<p>
Some of the protocol specifications referenced herein have their own
dependencies; developers need to consult the relevant specifications for
further information.
</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>
This document introduces no additional security considerations above and
beyond those defined in the documents on which it depends.
</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>This document requires no interaction with the &REGISTRAR;.</p>
</section1>
<section1 topic='Acknowledgements' anchor='ack'>
<p>
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.
</p>
</section1>
</xep>