JEP-0117: Intermediate IM Protocol Suite

This JEP defines a recommended suite of Jabber/XMPP protocols to be supported by intermediate instant messaging and presence applications.

WARNING: This Standards-Track JEP is Experimental. Publication as a Jabber Enhancement Proposal does not imply approval of this proposal by the Jabber Software 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.

JEP Information

Status: Experimental
Type: Standards Track
Number: 0117
Version: 0.4
Last Updated: 2004-08-18
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

Author Information

Peter Saint-Andre


Legal Notice

This Jabber Enhancement Proposal is copyright 1999 - 2004 by the Jabber Software Foundation (JSF) and is in full conformance with the JSF's Intellectual Property Rights Policy <>. 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 <>).

Discussion Venue

The preferred venue for discussion of this document is the Standards-JIG discussion list: <>.

Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core and XMPP IM 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 protocols defined in this JEP have been developed outside the Internet Standards Process and are to be understood as extensions to XMPP rather than as an evolution, development, or modification of XMPP itself.

Conformance Terms

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.

Table of Contents

1. Introduction
2. Requirements and Approach
3. Definition
4. Security Considerations
5. IANA Considerations
6. Jabber Registrar Considerations
Revision History

1. Introduction

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.

2. Requirements and Approach

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:

3. Definition

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
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:

4. Security Considerations

This JEP introduces no additional security considerations above and beyond those defined in the documents on which it depends.

5. IANA Considerations

This JEP requires no interaction with the Internet Assigned Numbers Authority (IANA) [11].

6. Jabber Registrar Considerations

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

2. JEP-0001: Jabber Enhancement Proposals <>.

3. JEP-0045: Multi-User Chat <>.

4. JEP-0071: XHTML-IM <>.

5. JEP-0096: File Transfer <>.

6. JEP-0115: Entity Capabilities <>.

7. JEP-0004: Data Forms <>.

8. JEP-0020: Feature Negotiation <>.

9. JEP-0047: In-Band Bytestreams <>.

10. JEP-0065: SOCKS5 Bytestreams <>.

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

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

Revision History

Version 0.4 (2004-08-18)

Clarified several matters in the text; changed name from "advanced" to "intermediate". (psa)

Version 0.3 (2004-03-24)

Updated to reflect approval of XMPP Core and XMPP IM. (psa)

Version 0.2 (2003-11-24)

Changed status to Deferred. (psa)

Version 0.1 (2003-09-08)

Initial version. (psa)