<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep xmlns="">
<header>
  <title>Intermediate IM Protocol Suite</title>
  <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.</abstract>
  
<legal>
<copyright>This XMPP Extension Protocol is copyright © 1999 – 2024 by the <link url="https://xmpp.org/">XMPP Standards Foundation</link> (XSF).</copyright>
<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.</permissions>
<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. ##</warranty>
<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.</liability>
<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 &lt;<link url="https://xmpp.org/about/xsf/ipr-policy">https://xmpp.org/about/xsf/ipr-policy</link>&gt; or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).</conformance>
</legal>
  <number>0117</number>
  <status>Obsolete</status>
  <type>Standards Track</type>
  <sig>Standards</sig>
  <approver>Council</approver>
  <dependencies>
    <spec>XMPP Core</spec>
    <spec>XMPP IM</spec>
    <spec>XEP-0045</spec>
    <spec>XEP-0071</spec>
    <spec>XEP-0073</spec>
    <spec>XEP-0096</spec>
    <spec>XEP-0115</spec>
  </dependencies>
  <supersedes/>
  <supersededby>
    <spec>XEP-0213</spec>
    <spec>XEP-0216</spec>
  </supersededby>
  <shortname>N/A</shortname>
  
  <author>
    <firstname>Peter</firstname>
    <surname>Saint-Andre</surname>
    <email>stpeter@stpeter.im</email>
    <jid>stpeter@jabber.org</jid>
    <uri>https://stpeter.im/</uri>
  </author>

  <revision>
    <version>1.1</version>
    <date>2007-10-30</date>
    <initials>psa</initials>
    <remark><p>Per a vote of the XMPP Council, changed status to Obsolete and referred implementors to XEP-0213 and XEP-0216.</p></remark>
  </revision>
  <revision>
    <version>1.0</version>
    <date>2005-07-21</date>
    <initials>psa</initials>
    <remark>Per a vote of the Jabber Council, advanced status to Draft.</remark>
  </revision>
  <revision>
    <version>0.7</version>
    <date>2005-06-08</date>
    <initials>psa</initials>
    <remark>Further clarified dependencies.</remark>
  </revision>
  <revision>
    <version>0.6</version>
    <date>2005-06-02</date>
    <initials>psa</initials>
    <remark>Per Council discussion, modified the XEP-0045 profile to require all MUC use cases.</remark>
  </revision>
  <revision>
    <version>0.5</version>
    <date>2005-04-21</date>
    <initials>psa</initials>
    <remark>Modified the XEP-0045 profile to require occupant use cases and instant room creation only.</remark>
  </revision>
  <revision>
    <version>0.4</version>
    <date>2004-08-18</date>
    <initials>psa</initials>
    <remark>Clarified several matters in the text; changed name from "advanced" to "intermediate".</remark>
  </revision>
  <revision>
    <version>0.3</version>
    <date>2004-03-24</date>
    <initials>psa</initials>
    <remark>Updated to reflect approval of XMPP Core and XMPP IM.</remark>
  </revision>
  <revision>
    <version>0.2</version>
    <date>2003-11-24</date>
    <initials>psa</initials>
    <remark>Changed status to Deferred.</remark>
  </revision>
  <revision>
    <version>0.1</version>
    <date>2003-09-08</date>
    <initials>psa</initials>
    <remark>Initial version.</remark>
  </revision>
</header>
<section1 topic="Introduction" anchor="intro">
  <p><em>Note: This protocol suite is obsolete. For updated protocol suites, refer to <span class="ref"><link url="https://xmpp.org/extensions/xep-0213.html">XMPP Intermediate IM Client 2008 (XEP-0213)</link></span> <note>XEP-0213: XMPP Intermediate IM Client 2008 &lt;<link url="https://xmpp.org/extensions/xep-0213.html">https://xmpp.org/extensions/xep-0213.html</link>&gt;.</note> and <span class="ref"><link url="https://xmpp.org/extensions/xep-0216.html">XMPP Intermediate IM Server 2008 (XEP-0216)</link></span> <note>XEP-0216: XMPP Intermediate IM Server 2008 &lt;<link url="https://xmpp.org/extensions/xep-0216.html">https://xmpp.org/extensions/xep-0216.html</link>&gt;.</note>.</em></p>
  <p>The <span class="ref"><link url="https://xmpp.org/extensions/xep-0073.html">Basic IM Protocol Suite (XEP-0073)</link></span> <note>XEP-0073: Basic IM Protocol Suite &lt;<link url="https://xmpp.org/extensions/xep-0073.html">https://xmpp.org/extensions/xep-0073.html</link>&gt;.</note> introduced the concept of a "protocol suite". This document extends the basic support specified in <span class="ref"><link url="https://xmpp.org/extensions/xep-0073.html">Basic IM Protocol Suite (XEP-0073)</link></span> <note>XEP-0073: Basic IM Protocol Suite &lt;<link url="https://xmpp.org/extensions/xep-0073.html">https://xmpp.org/extensions/xep-0073.html</link>&gt;.</note> by specifying an Intermediate IM Protocol Suite.</p>
</section1>
<section1 topic="Requirements and Approach" anchor="approach">
  <p>This document follows the same approach as <span class="ref"><link url="https://xmpp.org/extensions/xep-0073.html">Basic IM Protocol Suite (XEP-0073)</link></span> <note>XEP-0073: Basic IM Protocol Suite &lt;<link url="https://xmpp.org/extensions/xep-0073.html">https://xmpp.org/extensions/xep-0073.html</link>&gt;.</note>. 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.</p>
  <p>A protocol is deemed worthy of inclusion in this protocol suite if:</p>
  <ul>
    <li>It addresses common needs of instant messaging users that are addressed by virtually all other popular IM services or systems.</li>
    <li>It is more advanced than basic IM and presence.</li>
    <li>It has achieved a status of at least Draft within the XMPP Standards Foundation's standards process (as defined in <span class="ref"><link url="https://xmpp.org/extensions/xep-0001.html">XMPP Extension Protocols (XEP-0001)</link></span> <note>XEP-0001: XMPP Extension Protocols &lt;<link url="https://xmpp.org/extensions/xep-0001.html">https://xmpp.org/extensions/xep-0001.html</link>&gt;.</note>).</li>
  </ul>
</section1>
<section1 topic="Definition" anchor="def">
  <p>We define the Intermediate IM Protocol Suite as follows:</p>
  <table caption="Required and Recommended Specifications">
    <tr>
      <th>Specification</th>
      <th>Requirement Level</th>
    </tr>
    <tr>
      <td><strong>XEP-0073: Basic IM Protocol Suite</strong></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><span class="ref"><link url="https://xmpp.org/extensions/xep-0045.html">Multi-User Chat (XEP-0045)</link></span> <note>XEP-0045: Multi-User Chat &lt;<link url="https://xmpp.org/extensions/xep-0045.html">https://xmpp.org/extensions/xep-0045.html</link>&gt;.</note></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><span class="ref"><link url="https://xmpp.org/extensions/xep-0071.html">XHTML-IM (XEP-0071)</link></span> <note>XEP-0071: XHTML-IM &lt;<link url="https://xmpp.org/extensions/xep-0071.html">https://xmpp.org/extensions/xep-0071.html</link>&gt;.</note></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><span class="ref"><link url="https://xmpp.org/extensions/xep-0096.html">SI File Transfer (XEP-0096)</link></span> <note>XEP-0096: SI File Transfer &lt;<link url="https://xmpp.org/extensions/xep-0096.html">https://xmpp.org/extensions/xep-0096.html</link>&gt;.</note></td>
      <td>REQUIRED</td>
    </tr>
    <tr>
      <td><span class="ref"><link url="https://xmpp.org/extensions/xep-0115.html">Entity Capabilities (XEP-0115)</link></span> <note>XEP-0115: Entity Capabilities &lt;<link url="https://xmpp.org/extensions/xep-0115.html">https://xmpp.org/extensions/xep-0115.html</link>&gt;.</note></td>
      <td>REQUIRED</td>
    </tr>
  </table>
  <p>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):</p>
  <ul>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0004.html">Data Forms (XEP-0004)</link></span> <note>XEP-0004: Data Forms &lt;<link url="https://xmpp.org/extensions/xep-0004.html">https://xmpp.org/extensions/xep-0004.html</link>&gt;.</note></li>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0020.html">Feature Negotiation (XEP-0020)</link></span> <note>XEP-0020: Feature Negotiation &lt;<link url="https://xmpp.org/extensions/xep-0020.html">https://xmpp.org/extensions/xep-0020.html</link>&gt;.</note></li>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0047.html">In-Band Bytestreams (XEP-0047)</link></span> <note>XEP-0047: In-Band Bytestreams &lt;<link url="https://xmpp.org/extensions/xep-0047.html">https://xmpp.org/extensions/xep-0047.html</link>&gt;.</note></li>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0065.html">SOCKS5 Bytestreams (XEP-0065)</link></span> <note>XEP-0065: SOCKS5 Bytestreams &lt;<link url="https://xmpp.org/extensions/xep-0065.html">https://xmpp.org/extensions/xep-0065.html</link>&gt;.</note></li>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0068.html">Field Standardization for Data Forms (XEP-0068)</link></span> <note>XEP-0068: Field Data Standardization for Data Forms &lt;<link url="https://xmpp.org/extensions/xep-0068.html">https://xmpp.org/extensions/xep-0068.html</link>&gt;.</note></li>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0082.html">XMPP Date and Time Profiles (XEP-0082)</link></span> <note>XEP-0082: XMPP Date and Time Profiles &lt;<link url="https://xmpp.org/extensions/xep-0082.html">https://xmpp.org/extensions/xep-0082.html</link>&gt;.</note></li>
    <li><span class="ref"><link url="https://xmpp.org/extensions/xep-0095.html">Stream Initiation (XEP-0095)</link></span> <note>XEP-0095: Stream Initiation &lt;<link url="https://xmpp.org/extensions/xep-0095.html">https://xmpp.org/extensions/xep-0095.html</link>&gt;.</note></li>
  </ul>
  <p>In addition, because the intermediate suite builds on the basic suite, by definition all protocols required by <span class="ref"><link url="https://xmpp.org/extensions/xep-0073.html">Basic IM Protocol Suite (XEP-0073)</link></span> <note>XEP-0073: Basic IM Protocol Suite &lt;<link url="https://xmpp.org/extensions/xep-0073.html">https://xmpp.org/extensions/xep-0073.html</link>&gt;.</note> are also required by the intermediate suite (refer to <cite>XEP-0073</cite> for details).</p>
</section1>
<section1 topic="Security Considerations" anchor="security">
  <p>This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.</p>
</section1>
<section1 topic="IANA Considerations" anchor="iana">
  <p>This document requires no interaction with the <span class="ref"><link url="http://www.iana.org/">Internet Assigned Numbers Authority (IANA)</link></span> <note>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 &lt;<link url="http://www.iana.org/">http://www.iana.org/</link>&gt;.</note>.</p>
</section1>
<section1 topic="XMPP Registrar Considerations" anchor="registrar">
  <p>No namespaces or parameters need to be registered with the <span class="ref"><link url="https://xmpp.org/registrar/">XMPP Registrar</link></span> <note>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 &lt;<link url="https://xmpp.org/registrar/">https://xmpp.org/registrar/</link>&gt;.</note> as a result of this document.</p>
</section1>
</xep>
