Abstract: | This document defines the XMPP Intermedate IM Server 2008 compliance level. |
Author: | Peter Saint-Andre |
Copyright: | © 1999 - 2010 XMPP Standards Foundation. SEE LEGAL NOTICES. |
Status: | Obsolete |
Type: | Standards Track |
Version: | 1.0 |
Last Updated: | 2007-07-11 |
WARNING: This document has been obsoleted by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality are advised to implement the protocol that supersedes this one (if any).
1. Introduction
2. Definition
3. Implementation Notes
4. Security Considerations
5. IANA Considerations
6. XMPP Registrar Considerations
Appendices
A: Document Information
B: Author Information
C: Legal Notices
D: Relation to XMPP
E: Discussion Venue
F: Requirements Conformance
G: Notes
H: 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 IM Server 2008 certification level.
The XMPP Intermediate IM Server 2008 certification level is defined as follows:
Specification | Requirement Level |
---|---|
XMPP Basic Server 2008 [2] | REQUIRED |
Privacy Lists [3] | REQUIRED |
Multi-User Chat [4] | REQUIRED |
vcard-temp [5] | REQUIRED |
Personal Eventing Protocol [6] | RECOMMENDED |
Some of the protocol specifications referenced herein have their own dependencies; developers must refer to the relevant specifications for further information.
It is an implementation decision how to enable support for multi-user chat, e.g., directly or by means of an external component (see Jabber Component Protocol [7]).
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].
Series: XEP
Number: 0216
Publisher: XMPP Standards Foundation
Status:
Obsolete
Type:
Standards Track
Version: 1.0
Last Updated: 2007-07-11
Approving Body: XMPP Council
Dependencies: XEP-0212, XEP-0016, XEP-0045, XEP-0054, XEP-0163
Supersedes: None
Superseded By: XEP-0243
Short Name: N/A
Source Control:
HTML
RSS
This document in other formats:
XML
PDF
Email:
stpeter@jabber.org
JabberID:
stpeter@jabber.org
URI:
https://stpeter.im/
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 primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <editor@xmpp.org>.
The following requirements 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. 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://xmpp.org/xsf/>.
2. XEP-0212: XMPP Basic Server 2008 <http://xmpp.org/extensions/xep-0212.html>.
3. XEP-0016: Privacy Lists <http://xmpp.org/extensions/xep-0016.html>.
4. XEP-0045: Multi-User Chat <http://xmpp.org/extensions/xep-0045.html>.
5. XEP-0054: vcard-temp <http://xmpp.org/extensions/xep-0054.html>.
6. XEP-0163: Personal Eventing Protocol <http://xmpp.org/extensions/xep-0163.html>.
7. XEP-0114: Jabber Component Protocol <http://xmpp.org/extensions/xep-0114.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://xmpp.org/registrar/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/
Per a vote of the XMPP Council, advanced to Draft.
(psa)Added implementation notes.
(psa)Initial published version.
(psa)First draft.
(psa)END