This JEP defines a recommended suite of Jabber/XMPP protocols to be supported by intermediate instant messaging and presence applications.
NOTICE: This JEP is currently within Last Call or under consideration by the Jabber Council for advancement to the next stage in the JSF standards process. For further details, visit <http://www.jabber.org/council/queue.shtml>.
Status: Proposed
Type: Standards Track
Number: 0117
Version: 0.6
Last Updated: 2005-06-02
JIG: Standards JIG
Approving Body: Jabber Council
Dependencies: XMPP Core, XMPP IM, JEP-0045, JEP-0071, JEP-0073, JEP-0096, JEP-0115
Supersedes: None
Superseded By: None
Short Name: N/A
Email: stpeter@jabber.org
JID: stpeter@jabber.org
This Jabber Enhancement Proposal is copyright 1999 - 2005 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy <http://www.jabber.org/jsf/ipr-policy.shtml>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <http://www.opencontent.org/openpub/>).
The preferred venue for discussion of this document is the Standards-JIG discussion list: <http://mail.jabber.org/mailman/listinfo/standards-jig>.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the Jabber Software 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 JEP 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 keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Basic IM Protocol Suite [1] introduced the concept of a "protocol suite". This document extends the basic support specified in JEP-0073 by defining an Intermediate IM Protocol Suite.
This document follows the same approach as JEP-0073. By design, the Basic IM Protocol Suite does not include more advanced instant messaging functionality; the present document fills the need for a protocol suite that addresses such functionality.
A protocol is deemed worthy of inclusion in this protocol suite if:
We define the Intermediate IM Protocol Suite as follows:
Table 1: Required and Recommended Specifications
| Specification | Requirement Level |
|---|---|
| JEP-0073: Basic IM Protocol Suite | REQUIRED |
| Multi-User Chat [3] | REQUIRED |
| XHTML-IM [4] | REQUIRED |
| File Transfer [5] | REQUIRED |
| Entity Capabilities [6] | REQUIRED |
Note well that the foregoing protocols apply to clients only (i.e., they do not introduce new requirements for servers). In addition, these protocols have their own dependencies, which include:
This JEP introduces no additional security considerations above and beyond those defined in the documents on which it depends.
This JEP requires no interaction with the Internet Assigned Numbers Authority (IANA) [11].
No namespaces or parameters need to be registered with the Jabber Registrar [12] as a result of this JEP.
1. JEP-0073: Basic IM Protocol Suite <http://www.jabber.org/jeps/jep-0073.html>.
2. JEP-0001: Jabber Enhancement Proposals <http://www.jabber.org/jeps/jep-0001.html>.
3. JEP-0045: Multi-User Chat <http://www.jabber.org/jeps/jep-0045.html>.
4. JEP-0071: XHTML-IM <http://www.jabber.org/jeps/jep-0071.html>.
5. JEP-0096: File Transfer <http://www.jabber.org/jeps/jep-0096.html>.
6. JEP-0115: Entity Capabilities <http://www.jabber.org/jeps/jep-0115.html>.
7. JEP-0004: Data Forms <http://www.jabber.org/jeps/jep-0004.html>.
8. JEP-0020: Feature Negotiation <http://www.jabber.org/jeps/jep-0020.html>.
9. JEP-0047: In-Band Bytestreams <http://www.jabber.org/jeps/jep-0047.html>.
10. JEP-0065: SOCKS5 Bytestreams <http://www.jabber.org/jeps/jep-0065.html>.
11. 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/>.
12. The Jabber Registrar maintains a list of reserved Jabber protocol namespaces as well as registries of parameters used in the context of protocols approved by the Jabber Software Foundation. For further information, see <http://www.jabber.org/registrar/>.
END