xeps/xep-0211.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 Client 2008</title>
  <abstract>This document defines the XMPP Basic Client 2008 compliance level.</abstract>
  &LEGALNOTICE;
  <number>0211</number>
  <status>Draft</status>
  <type>Standards Track</type>
  <sig>Standards</sig>
  <dependencies>
    <spec>XMPP Core</spec>
    <spec>XMPP IM</spec>
    <spec>XEP-0030</spec>
    <spec>XEP-0106</spec>
    <spec>XEP-0115</spec>
    <spec>XEP-0138</spec>
  </dependencies>
  <supersedes/>
  <supersededby/>
  <shortname>N/A</shortname>
  &stpeter;
  <revision>
    <version>1.0</version>
    <date>2007-07-11</date>
    <initials>psa</initials>
    <remark><p>Per a vote of the XMPP Council, advanced to Draft.</p></remark>
  </revision>
  <revision>
    <version>0.6</version>
    <date>2007-07-11</date>
    <initials>psa</initials>
    <remark><p>Changed XEP-0115 to recommended.</p></remark>
  </revision>
  <revision>
    <version>0.5</version>
    <date>2007-06-18</date>
    <initials>psa</initials>
    <remark><p>Removed implementation note about XMPP ICA.</p></remark>
  </revision>
  <revision>
    <version>0.4</version>
    <date>2007-06-14</date>
    <initials>psa</initials>
    <remark><p>Per community discussion, changed XMPP Core and XMPP IM references back to RFCs with recommendation for developers to also consult bis drafts; added reference to XEP-0178; suggested bundling of root certificate for XMPP ICA.</p></remark>
  </revision>
  <revision>
    <version>0.3</version>
    <date>2007-06-11</date>
    <initials>psa</initials>
    <remark><p>Changed XMPP Core and XMPP IM references to bis drafts; added implementation notes.</p></remark>
  </revision>
  <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 Client 2008 certification level.</p>
</section1>
<section1 topic='Definition' anchor='def'>
  <p>The XMPP Basic Client 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>&xep0106;</strong></td>
      <td>RECOMMENDED</td>
    </tr>
    <tr>
      <td><strong>&xep0115;</strong></td>
      <td>RECOMMENDED</td>
    </tr>
    <tr>
      <td><strong>&xep0138;</strong></td>
      <td>RECOMMENDED</td>
    </tr>
  </table>
  <p>* Note: 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>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
  <p>Some of the protocol specifications referenced herein have their own dependencies; developers must refer to 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>