This document defines the XMPP Intermediate Client 2008 compliance level.
WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems should not deploy implementations of this protocol until it advances to a status of Draft.
Series: XEP
Number: 0213
Publisher: XMPP Standards Foundation
Status:
Experimental
Type:
Standards Track
Version: 0.1
Last Updated: 2007-04-20
Approving Body: XMPP Council
Dependencies: XMPP Core, XMPP IM, XEP-0045, XEP-0071, XEP-0085
Supersedes: None
Superseded By: None
Short Name: N/A
Wiki Page: <http://wiki.jabber.org/index.php/XMPP Intermediate Client 2008 (XEP-0213)>
Email:
stpeter@jabber.org
JabberID:
stpeter@jabber.org
This XMPP Extension Protocol is copyright 1999 - 2007 by the XMPP Standards Foundation (XSF) and is in full conformance with the XSF's Intellectual Property Rights Policy <http://www.xmpp.org/extensions/ipr-policy.shtml>. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<http://creativecommons.org/licenses/by/2.5/>).
The preferred venue for discussion of this document is the Standards discussion list: <http://mail.jabber.org/mailman/listinfo/standards>.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The following keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
1. Introduction
2. Definition
3. Security Considerations
4. IANA Considerations
5. XMPP Registrar Considerations
Notes
Revision History
The XMPP Standards Foundation (XSF) [1] defines protocol suites for the purpose of compliance testing and software certification. This document specifies the XMPP Intermediate Client 2008 certification level.
The XMPP Intermediate Client 2008 certification level is defined as follows:
Table 1: Required and Recommended Specifications
| Specification | Requirement Level |
|---|---|
| XMPP Basic Client 2008 | REQUIRED |
| Multi-User Chat [2] | REQUIRED |
| XHTML-IM [3] | REQUIRED |
| Chat State Notifications [4] | REQUIRED |
Note: These protocols have their own dependencies, which include the following XEPs (as well as various IETF RFCs and W3C specifications):
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 the Internet Assigned Numbers Authority (IANA) [8].
This document requires no interaction with the XMPP Registrar [9].
1. The XMPP Standards Foundation (XSF) is an independent, non-profit membership organization that develops open extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP). For further information, see <http://www.xmpp.org/xsf/>.
2. XEP-0045: Multi-User Chat <http://www.xmpp.org/extensions/xep-0045.html>.
3. XEP-0071: XHTML-IM <http://www.xmpp.org/extensions/xep-0071.html>.
4. XEP-0085: Chat State Notifications <http://www.xmpp.org/extensions/xep-0085.html>.
5. XEP-0004: Data Forms <http://www.xmpp.org/extensions/xep-0004.html>.
6. XEP-0068: Field Data Standardization for Data Forms <http://www.xmpp.org/extensions/xep-0068.html>.
7. XEP-0082: XMPP Date and Time Profiles <http://www.xmpp.org/extensions/xep-0082.html>.
8. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
9. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <http://www.xmpp.org/registrar/>.
Initial published version.
(psa)END