xeps/xep-0212.xml

<?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 Basic Server 2008</title>
  <abstract>This document defines the XMPP Basic Server 2008 compliance level.</abstract>
  &LEGALNOTICE;
  <number>0212</number>
  <status>Experimental</status>
  <type>Standards Track</type>
  <sig>Standards</sig>
  <dependencies>
    <spec>XMPP Core</spec>
    <spec>XMPP IM</spec>
    <spec>XEP-0030</spec>
    <spec>XEP-0078</spec>
    <spec>XEP-0086</spec>
    <spec>XEP-0106</spec>
    <spec>XEP-0115</spec>
    <spec>XEP-0138</spec>
  </dependencies>
  <supersedes/>
  <supersededby/>
  <shortname>N/A</shortname>
  &stpeter;
  <revision>
    <version>0.2</version>
    <date>2007-05-11</date>
    <initials>psa</initials>
    <remark><p>Added JID Escaping (XEP-0106) and Stream Compression (XEP-0138) as recommended.</p></remark>
  </revision>
  <revision>
    <version>0.1</version>
    <date>2007-04-20</date>
    <initials>psa</initials>
    <remark><p>Initial published version.</p></remark>
  </revision>
  <revision>
    <version>0.0.1</version>
    <date>2007-03-30</date>
    <initials>psa</initials>
    <remark><p>First draft, split from XEP-0073.</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 XMPP Basic Server 2008 certification level.</p>
</section1>
<section1 topic='Definition' anchor='def'>
  <p>The XMPP Basic Server 2008 certification level is defined as follows:</p>
  <table caption='Required and Recommended Specifications'>
    <tr>
      <th>Specification</th>
      <th>Requirement Level</th>
    </tr>
    <tr>
      <td><strong>&rfc3920;</strong></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><strong>&rfc3921;</strong></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><strong>&xep0030;</strong></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><strong>&xep0078;</strong></td>
      <td>RECOMMENDED*</td>
    </tr>
    <tr>
      <td><strong>&xep0086;</strong></td>
      <td>RECOMMENDED*</td>
    </tr>
    <tr>
      <td><strong>&xep0106;</strong></td>
      <td>RECOMMENDED</td>
    </tr>
    <tr>
      <td><strong>&xep0138;</strong></td>
      <td>RECOMMENDED</td>
    </tr>
  </table>
  <p>Some of these protocols have their own dependencies. In addition, the XMPP RFCs are currently being revised to incorporate errata and feedback based on implementation experience; therefore implementors are advised to refer to &rfc3920bis; and &rfc3921bis; for the most up to date specifications and references.</p>
  <p>* Note: Support for XEP-0078 and XEP-0086 is recommended for backward compatibility only. It is likely that compliance definitions for future years will remove these recommendations.</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>