XEP-0117: Intermediate IM Protocol Suite

Abstract:This document defines a recommended suite of Jabber/XMPP protocols to be supported by intermediate instant messaging and presence applications. Note: This protocol suite has been obsoleted by XEP-0213 and XEP-0216.
Author:Peter Saint-Andre
Copyright:© 1999 - 2010 XMPP Standards Foundation. SEE LEGAL NOTICES.
Status:Obsolete
Type:Standards Track
Version:1.1
Last Updated:2007-10-30

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

Table of Contents


1. Introduction
2. Requirements and Approach
3. Definition
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

1. Introduction

Note: This protocol suite is obsolete. For updated protocol suites, refer to XMPP Intermediate IM Client 2008 [1] and XMPP Intermediate IM Server 2008 [2].

The Basic IM Protocol Suite [3] introduced the concept of a "protocol suite". This document extends the basic support specified in XEP-0073 by specifying an Intermediate IM Protocol Suite.

2. Requirements and Approach

This document follows the same approach as XEP-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
XEP-0073: Basic IM Protocol Suite REQUIRED
Multi-User Chat [5] REQUIRED
XHTML-IM [6] REQUIRED
SI File Transfer [7] REQUIRED
Entity Capabilities [8] 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 the following XEPs (as well as various IETF RFCs and W3C specifications):

In addition, because the intermediate suite builds on the basic suite, by definition all protocols required by XEP-0073 are also required by the intermediate suite (refer to XEP-0073 for details).

4. Security Considerations

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

5. IANA Considerations

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

6. XMPP Registrar Considerations

No namespaces or parameters need to be registered with the XMPP Registrar [17] as a result of this document.

Appendices

Appendix A: Document Information

Series: XEP
Number: 0117
Publisher: XMPP Standards Foundation
Status: Obsolete
Type: Standards Track
Version: 1.1
Last Updated: 2007-10-30
Approving Body: XMPP Council
Dependencies: XMPP Core, XMPP IM, XEP-0045, XEP-0071, XEP-0073, XEP-0096, XEP-0115
Supersedes: None
Superseded By: XEP-0213, XEP-0216
Short Name: N/A
Source Control: HTML  RSS
This document in other formats: XML  PDF

Appendix B: Author Information

Peter Saint-Andre

Email: stpeter@jabber.org
JabberID: stpeter@jabber.org
URI: https://stpeter.im/

Appendix C: Legal Notices

Copyright

This XMPP Extension Protocol is copyright © 1999 - 2010 by the XMPP Standards Foundation (XSF).

Permissions

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <http://xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XMPP Standards Foundation, 1899 Wynkoop Street, Suite 600, Denver, CO 80202 USA).

Appendix D: Relation to XMPP

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.

Appendix E: Discussion Venue

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

Appendix F: Requirements Conformance

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

Appendix G: Notes

1. XEP-0213: XMPP Intermediate IM Client 2008 <http://xmpp.org/extensions/xep-0213.html>.

2. XEP-0216: XMPP Intermediate IM Server 2008 <http://xmpp.org/extensions/xep-0216.html>.

3. XEP-0073: Basic IM Protocol Suite <http://xmpp.org/extensions/xep-0073.html>.

4. XEP-0001: XMPP Extension Protocols <http://xmpp.org/extensions/xep-0001.html>.

5. XEP-0045: Multi-User Chat <http://xmpp.org/extensions/xep-0045.html>.

6. XEP-0071: XHTML-IM <http://xmpp.org/extensions/xep-0071.html>.

7. XEP-0096: SI File Transfer <http://xmpp.org/extensions/xep-0096.html>.

8. XEP-0115: Entity Capabilities <http://xmpp.org/extensions/xep-0115.html>.

9. XEP-0004: Data Forms <http://xmpp.org/extensions/xep-0004.html>.

10. XEP-0020: Feature Negotiation <http://xmpp.org/extensions/xep-0020.html>.

11. XEP-0047: In-Band Bytestreams <http://xmpp.org/extensions/xep-0047.html>.

12. XEP-0065: SOCKS5 Bytestreams <http://xmpp.org/extensions/xep-0065.html>.

13. XEP-0068: Field Data Standardization for Data Forms <http://xmpp.org/extensions/xep-0068.html>.

14. XEP-0082: XMPP Date and Time Profiles <http://xmpp.org/extensions/xep-0082.html>.

15. XEP-0095: Stream Initiation <http://xmpp.org/extensions/xep-0095.html>.

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

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

Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 1.1 (2007-10-30)

Per a vote of the XMPP Council, changed status to Obsolete and referred implementors to XEP-0213 and XEP-0216.

(psa)

Version 1.0 (2005-07-21)

Per a vote of the Jabber Council, advanced status to Draft. (psa)

Version 0.7 (2005-06-08)

Further clarified dependencies. (psa)

Version 0.6 (2005-06-02)

Per Council discussion, modified the XEP-0045 profile to require all MUC use cases. (psa)

Version 0.5 (2005-04-21)

Modified the XEP-0045 profile to require occupant use cases and instant room creation only. (psa)

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)

END