1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-16 06:15:07 -05:00
xeps/xep-0270.xml

163 lines
5.8 KiB
XML
Raw Normal View History

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>XMPP Compliance Suites 2010</title>
<abstract>This document defines XMPP protocol compliance levels for 2010.</abstract>
&LEGALNOTICE;
<number>0270</number>
<status>Proposed</status>
<type>Standards Track</type>
<sig>Standards</sig>
<dependencies>
<spec>XMPP Core</spec>
<spec>XMPP IM</spec>
<spec>XEP-0016</spec>
<spec>XEP-0030</spec>
<spec>XEP-0045</spec>
<spec>XEP-0054</spec>
<spec>XEP-0114</spec>
<spec>XEP-0124</spec>
<spec>XEP-0138</spec>
<spec>XEP-0163</spec>
<spec>XEP-0191</spec>
<spec>XEP-0206</spec>
</dependencies>
<supersedes/>
<supersededby/>
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>0.1</version>
<date>2009-05-20</date>
<initials>psa</initials>
<remark><p>Initial published version, copied and modified from XEP-0242 and XEP-0243.</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 2010 compliance levels for XMPP clients and servers. Unless qualified where explicitly noted, support for the listed specifications is REQUIRED for compliance purposes.</p>
</section1>
<section1 topic='Compliance Levels' anchor='levels'>
<table caption='XMPP Compliance Levels for 2010'>
<tr>
<th>Spec</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
</tr>
<tr>
<td>&rfc3920; *</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
</tr>
<tr>
<td>&rfc3921; *</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
</tr>
<tr>
<td>&xep0030;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
</tr>
<tr>
<td>&xep0114;</td>
<td align='center'>&#10003;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;</td>
<td align='center'>N/A</td>
</tr>
<tr>
<td>&xep0016;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10005;</td>
</tr>
<tr>
<td>&xep0191;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10005;</td>
</tr>
<tr>
<td>&xep0124;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003; **</td>
<td align='center'>&#10005;</td>
</tr>
<tr>
<td>&xep0206;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003; **</td>
<td align='center'>&#10005;</td>
</tr>
<tr>
<td>&xep0054;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
</tr>
<tr>
<td>&xep0163;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003;</td>
<td align='center'>&#10003;</td>
</tr>
<tr>
<td>&xep0045;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10005;</td>
<td align='center'>&#10003; **</td>
<td align='center'>&#10003; ***</td>
</tr>
<tr>
<td>&xep0115;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;</td>
</tr>
<tr>
<td>&xep0085;</td>
<td align='center'>N/A</td>
<td align='center'>&#10005;</td>
<td align='center'>N/A</td>
<td align='center'>&#10003;</td>
</tr>
</table>
<p>* RFC 3920 and RFC 3921 are currently being revised to correct errors, clarify matters that were underspecified, and incorporate feedback based on implementation and deployment experience gained since RFC 3920 and RFC 3921 were published in 2004. Although the compliance level specified herein refers to RFC 3920 and RFC 3921, developers are also advised to consult &rfc3920bis; and &rfc3921bis;, which provide the most up-to-date and accurate description the core XMPP protocols.</p>
<p>** Support can be enabled via an external component or an internal server module/plugin.</p>
<p>*** Support for the Entity Use Cases and Occupant Use Cases is REQUIRED; support for the remaining use cases is RECOMMENDED.</p>
</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>
<p>Developers are advised to refer to &xep0178; regarding proper implementation of the SASL EXTERNAL mechanism in XMPP.</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>
</xep>