%ents; ]>
XMPP Basic Client 2008 This document defines the XMPP Basic Client 2008 compliance level. &LEGALNOTICE; 0211 Proposed Standards Track Standards XMPP Core XMPP IM XEP-0030 XEP-0106 XEP-0115 XEP-0138 N/A &stpeter; 0.5 2007-06-18 psa

Removed implementation note about XMPP ICA.

 0.4 2007-06-14 psa

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.

 0.3 2007-06-11 psa

Changed XMPP Core and XMPP IM references to bis drafts; added implementation notes.

 0.2 2007-05-11 psa

Added JID Escaping (XEP-0106) and Stream Compression (XEP-0138) as recommended.

 0.1 2007-04-20 psa

Initial published version.

 0.0.1 2007-03-30 psa

First draft, split from XEP-0073.

The &XSF; defines protocol suites for the purpose of compliance testing and software certification. This document specifies the XMPP Basic Client 2008 certification level.

The XMPP Basic Client 2008 certification level is defined as follows:

Specification Requirement Level
&rfc3920; REQUIRED *
&rfc3921; REQUIRED *
&xep0030; REQUIRED
&xep0106; RECOMMENDED
&xep0115; REQUIRED
&xep0138; RECOMMENDED

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

Some of the protocol specifications referenced herein have their own dependencies; developers must refer to 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;.