<xep-infos><xep accepted="true"><number>1</number><title>XMPP Extension Protocols</title><abstract>This document defines the standards process followed by the XMPP Standards Foundation.</abstract><type>Procedural</type><status>Active</status><approver>Board</approver><last-revision><date>2024-03-11</date><version>1.25.0</version><initials>XEP Editor: dg</initials><remark>Add note that editorial changes do not affect Deferred state</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>2</number><title>Special Interest Groups (SIGs)</title><abstract>A definition of Special Interest Groups within the XMPP Standards Foundation.</abstract><type>Procedural</type><status>Active</status><approver>Board</approver><last-revision><date>2002-01-11</date><version>1.1</version><initials>psa</initials><remark>Clarified some details and added information about cut-offs for inactivity.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>3</number><title>Proxy Accept Socket Service (PASS)</title><abstract>This document defines a method for relaying media via proxies on the Jabber/XMPP network.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>pass</shortname><last-revision><date>2009-06-03</date><version>1.4</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>4</number><title>Data Forms</title><abstract>This specification defines an XMPP protocol extension for data forms that can be used in workflows such as service configuration as well as for application-specific data description and reporting. The protocol includes lightweight semantics for forms processing (such as request, response, submit, and cancel), defines several common field types (boolean, list options with single or multiple choice, text with single line or multiple lines, single or multiple JabberIDs, hidden fields, etc.), provides extensibility for future data types, and can be embedded in a wide range of applications. The protocol is not intended to provide complete forms-processing functionality as is provided in the W3C XForms technology, but instead provides a basic subset of such functionality for use by XMPP entities.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>x-data</shortname><last-revision><date>2024-08-30</date><version>2.13.2</version><initials>gk</initials><remark>Add section on empty and absent values.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>5</number><title>Jabber Interest Groups</title><abstract>This is the official list and summary information of the Jabber Interest Groups.</abstract><type>Informational</type><status>Obsolete</status><approver>Council</approver><last-revision><date>2002-05-08</date><version>1.1</version><initials>psa</initials><remark>Changed Status to Obsolete per approval of XEP-0019.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>6</number><title>Profiles</title><abstract>A proposal for a more powerful and extensible protocol for the management of personal information within Jabber.</abstract><type>SIG Formation</type><status>Obsolete</status><approver>Board</approver><last-revision><date>2002-05-08</date><version>1.1</version><initials>psa</initials><remark>Changed Status to Obsolete per approval of XEP-0019.</remark></last-revision><sig>Forms, Security</sig></xep><xep accepted="true"><number>7</number><title>Conferencing SIG</title><abstract>A proposal for a Jabber Interest Group that will discuss the protocol for implementing many-to-many communications.</abstract><type>SIG Proposal</type><status>Obsolete</status><approver>Board</approver><last-revision><date>2002-05-08</date><version>1.1</version><initials>psa</initials><remark>Changed Status to Obsolete per approval of XEP-0019.</remark></last-revision><sig>Conferencing</sig></xep><xep accepted="true"><number>8</number><title>IQ-Based Avatars</title><abstract>This specification provides historical documentation of an IQ-based protocol for exchanging user avatars.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0084</spec><spec>XEP-0153</spec></supersededby><last-revision><date>2022-03-08</date><version>0.3.1</version><initials>egp</initials><remark>* Move from deferred to obsolete.
* Add the two superseding specifications.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>9</number><title>Jabber-RPC</title><abstract>This specification defines an XMPP protocol extension for transporting XML-RPC encoded requests and responses between two XMPP entities. The protocol supports all syntax and semantics of XML-RPC except that it uses XMPP instead of HTTP as the underlying transport.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>jabber-rpc</shortname><last-revision><date>2021-03-04</date><version>2.2.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>10</number><title>Whiteboarding SIG</title><abstract>A proposal to form a SIG to develop a protocol for whiteboarding over Jabber.</abstract><type>SIG Formation</type><status>Obsolete</status><approver>Board</approver><last-revision><date>2002-05-08</date><version>1.1</version><initials>psa</initials><remark>Changed Status to Obsolete per approval of XEP-0019.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>11</number><title>Jabber Browsing</title><abstract>This document defines a way to describe information about Jabber entities and the relationships between entities. Note: This document is superseded by XEP-0030: Service Discovery.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>iq-browse</shortname><supersededby><spec>XEP-0030</spec></supersededby><last-revision><date>2021-03-04</date><version>1.3.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>12</number><title>Last Activity</title><abstract>This specification defines an XMPP protocol extension for communicating information about the last activity associated with an XMPP entity. It is typically used by an IM client to retrieve the most recent presence information from an offline contact by sending a last activity request to the server that hosts the account controlled by the contact.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>iq-last</shortname><last-revision><date>2008-11-26</date><version>2.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Final; clarified a few small points in the text; added a reference to XEP-0115.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>13</number><title>Flexible Offline Message Retrieval</title><abstract>This specification defines an XMPP protocol extension for flexible, POP3-like handling of offline messages. The protocol enables a connecting client to retrieve its offline messages on login in a controlled fashion, without receiving a flood of messages. Messages can also be left on the server for later retrieval.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>offline</shortname><last-revision><date>2021-05-04</date><version>1.3</version><initials>XEP Editor (jsc)</initials><remark>Deprecate after council vote of 2021-03-31</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>14</number><title>Message Tone</title><abstract>A proposal for including the sender's tone in messages.</abstract><type>Standards Track</type><status>Rejected</status><approver>Council</approver><last-revision><date>2002-01-16</date><version>0.2</version><initials>psa</initials><remark>First release to CVS, including editorial changes and assignment of number.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>15</number><title>Account Transfer</title><abstract>A proposal for enabling the ability to transfer an account from one Jabber server to another.</abstract><type>Standards Track</type><status>Rejected</status><approver>Council</approver><last-revision><date>2002-04-18</date><version>0.4</version><initials>cwc</initials><remark>Cleaned up the open issues and concerns section.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>16</number><title>Privacy Lists</title><abstract>This specification defines an XMPP protocol extension for enabling or disabling communication with other entities on a network. The protocol, which was first standardized in Section 10 of RFC 3921, can be used to block communication with unknown or undesirable entities. Blocking can be based on Jabber Identifier, subscription state, or roster group. The blocked stanzas can be messages, IQs, inbound or outbound presence stanzas, or all stanzas. The protocol also enables an entity to create, modify, or delete its privacy lists, apply different lists to different connected resources, define a default list, and decline the use of any privacy list during a particular communications session.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>privacy</shortname><supersededby><spec>XEP-0191</spec></supersededby><last-revision><date>2017-05-20</date><version>1.7</version><initials>XEP Editor: ssw</initials><remark>Deprecating by vote of the council.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>17</number><title>Naive Packet Framing Protocol</title><abstract>An intermediate method for more efficient framing of the Jabber XML Stream.</abstract><type>Informational</type><status>Rejected</status><approver>Council</approver><last-revision><date>2002-02-19</date><version>0.3</version><initials>mfl</initials><remark>Continued improvement and specification.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>18</number><title>Invisible Presence</title><abstract>Documentation of invisible presence.</abstract><type>Informational</type><status>Rejected</status><approver>Council</approver><last-revision><date>2003-09-26</date><version>0.2</version><initials>bs</initials><remark>Updated to focus solely on &lt;presence type='invisible'/&gt;.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>19</number><title>Streamlining the SIGs</title><abstract>This document proposes to streamline the existing Special Interest Groups (SIGs).</abstract><type>Procedural</type><status>Active</status><approver>Board</approver><last-revision><date>2022-11-03</date><version>1.1</version><initials>pep</initials><remark>Replaced shtml link.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>20</number><title>Feature Negotiation</title><abstract>This specification defines an XMPP protocol extension that enables two entities to mutually negotiate feature options, such as parameters related to a file transfer or a communications session.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>feature-neg</shortname><last-revision><date>2018-03-07</date><version>1.6</version><initials>jwi (Editor)</initials><remark>Deprecated as per Council vote on 2018-03-07.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>21</number><title>Jabber Event Notification Service (ENS)</title><abstract>A generic publish-and-subscribe service for Jabber.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0060</spec></supersededby><last-revision><date>2003-04-22</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, the status of this document has been changed to Retracted since it has been superseded by XEP-0060.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>22</number><title>Message Events</title><abstract>This document defines an XMPP protocol extension used to request and respond to events relating to the delivery, display, and composition of messages. Note: This specification has been obsoleted in favor of XEP-0085 and XEP-0184.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>x-event</shortname><supersededby><spec>XEP-0085</spec><spec>XEP-0184</spec></supersededby><last-revision><date>2009-05-27</date><version>1.4</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>23</number><title>Message Expiration</title><abstract>This specification documents an historical protocol that was used to specify expiration dates for messages; this protocol has been deprecated in favor of XEP-0079: Advanced Message Processing.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>x-expire</shortname><supersededby><spec>XEP-0079</spec></supersededby><last-revision><date>2009-06-03</date><version>1.3</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>24</number><title>Publish/Subscribe</title><abstract>A publish-subscribe protocol for Jabber.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0060</spec></supersededby><last-revision><date>2003-04-22</date><version>0.2</version><initials>psa</initials><remark>At the request of the authors, the status of this document has been changed to Retracted since it has been superseded by XEP-0060.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>25</number><title>Jabber HTTP Polling</title><abstract>This document defines an XMPP protocol extension that enables access to a Jabber server from behind firewalls which do not allow outgoing sockets on port 5222, via HTTP requests.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>httppoll</shortname><supersededby><spec>XEP-0124</spec></supersededby><last-revision><date>2009-06-03</date><version>1.2</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>26</number><title>Internationalization (I18N)</title><abstract>NOTE WELL: this document was retracted on 2003-11-05 since the topic is addressed definitively in XMPP Core. Please refer to XMPP Core for further information.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XMPP Core</spec></supersededby><last-revision><date>2003-11-05</date><version>0.2</version><initials>psa</initials><remark>The status of this document has been changed to Retracted since it has been superseded by XMPP Core.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>27</number><title>Current Jabber OpenPGP Usage</title><abstract>This document outlines the current usage of OpenPGP for messaging and presence.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>openpgp</shortname><last-revision><date>2014-03-14</date><version>1.4</version><initials>editor (mam)</initials><remark>Per a vote of the XMPP Council, changed status from Active to Deprecated to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>28</number><title>No Such XEP</title><abstract>This document was removed from the XSF website and source control at the request of the author.</abstract><type>Informational</type><status>Retracted</status><approver>Council</approver><last-revision><date>2001-08-20</date><version>0.1</version><initials>none</initials><remark>No such specification.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>29</number><title>Definition of Jabber Identifiers (JIDs)</title><abstract>Note well: this document was superseded by RFC 3920 and RFC 6122, which in turn have been superseded by RFC 7622. This document defines the exact nature of a Jabber Identifier (JID).</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>RFC 7622</spec></supersededby><last-revision><date>2022-09-23</date><version>1.1.1</version><initials>gk</initials><remark>Add references to RFC 7622, which has superseded RFC 6122.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>30</number><title>Service Discovery</title><abstract>This specification defines an XMPP protocol extension for discovering information about other XMPP entities. Two kinds of information can be discovered: (1) the identity and capabilities of an entity, including the protocols and features it supports; and (2) the items associated with an entity, such as the list of rooms hosted at a multi-user chat service.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>disco</shortname><supersedes><spec>XEP-0011</spec><spec>XEP-0094</spec></supersedes><last-revision><date>2024-04-30</date><version>2.5.0</version><initials>pep</initials><remark>Add note about some entities not advertising the  feature.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>31</number><title>A Framework For Securing Jabber Conversations</title><abstract>Although the value and utility of contemporary instant messaging systems, like Jabber, are now indisputable, current security features to protect message data are generally inadequate for many deployments; this is particularly true in security conscious environments like large, commercial enterprises and government agencies. These current features suffer from issues of scalability, usability, and supported features. Furthermore, there is a lack of standardization. We present a protocol to allow communities of Jabber users to apply cryptographic protection to selected conversation data.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2002-07-09</date><version>0.2</version><initials>PCL</initials><remark>
updated to reflect group consensus to incorporate XML Encryption, as well
as other group comments from Draft 0.9.
</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>32</number><title>Jabber URI Scheme</title><abstract>A URI scheme for Jabber communications.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>RFC 5122</spec></supersededby><last-revision><date>2003-09-02</date><version>0.4</version><initials>psa</initials><remark>Retracted the document, since it is superseded by draft-ietf-xmpp-uri, an Internet-Draft produced by the IETF's XMPP WG.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>33</number><title>Extended Stanza Addressing</title><abstract>This specification defines an XMPP protocol extension that enables entities to include RFC822-style address headers within XMPP stanzas in order to specify multiple recipients or sub-addresses.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>address</shortname><last-revision><date>2017-01-11</date><version>1.2.1</version><initials>cs (XEP Editor: ssw)</initials><remark>Clarify Reply Handling, add 'ofrom' type and fix examples</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>34</number><title>SASL Integration</title><abstract>NOTE WELL: this specification was retracted on 2003-11-05 since the topic is addressed definitively in XMPP Core. Please refer to XMPP Core for further information.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XMPP Core</spec></supersededby><last-revision><date>2003-11-05</date><version>1.1</version><initials>psa</initials><remark>The status of this specification has been changed to Retracted since it has been superseded by XMPP Core.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>35</number><title>SSL/TLS Integration</title><abstract>NOTE WELL: this specification was retracted on 2003-11-05 since the topic is addressed definitively in XMPP Core. Please refer to XMPP Core for further information.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XMPP Core</spec></supersededby><last-revision><date>2003-11-05</date><version>0.2</version><initials>psa</initials><remark>The status of this specification has been changed to Retracted since it has been superseded by XMPP Core.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>36</number><title>Pub-Sub Subscriptions</title><abstract>A proposal for the subscribe half of a publish-subscribe protocol within Jabber.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0060</spec></supersededby><last-revision><date>2003-04-22</date><version>0.2</version><initials>psa</initials><remark>At the request of the authors, the status of this specification has been changed to Retracted since it has been superseded by XEP-0060.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>37</number><title>DSPS - Data Stream Proxy Service</title><abstract>A proposal for proxy support in Jabber.</abstract><type>Standards Track</type><status>Rejected</status><approver>Council</approver><last-revision><date>2016-10-04</date><version>0.8.1</version><initials>egp</initials><remark>Made the revision&#8217;s version element include only the actual version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>38</number><title>Icon Styles</title><abstract>A protocol for specifying exchangeable styles of emoticons and genicons within Jabber IM clients.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>Unicode</spec><spec>XEP-0231</spec></supersededby><last-revision><date>2022-03-08</date><version>0.5.1</version><initials>egp</initials><remark>Obsolete due to the omnipresence of Unicode emoji, as well as Bits of Binary stickers.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>39</number><title>Statistics Gathering</title><abstract>A protocol to enable gathering statistics from Jabber servers and components.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2002-11-05</date><version>0.6.0</version><initials>rkd</initials><remark>
        Corrected David Sutton's JID and email.
        It has been pointed out to me by amoungst others Rob Norris that things
        such as lists of JIDs and lists in general are really the province of
        disco and browse and that at least one of the suggested 'core'
        statistics doesn't make sense for all components so removed these from
        the document.
        This namespace was starting to become a generic data gathering namespace
        and we already have one of those, so I've reworked yet again hopefully
        for the final time it should now be simpler to implement and more
        consistent in all cases.
      </remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>40</number><title>Jabber Robust Publish-Subscribe</title><abstract>Note: This proposal has been superseded by XEP-0060; please refer to that document for the successor protocol.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0060</spec></supersededby><last-revision><date>2004-07-26</date><version>0.2</version><initials>psa</initials><remark>Formally retracted this proposal in favor of XEP-0060: Publish-Subscribe.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>41</number><title>Reliable Entity Link</title><abstract>Protocol for linking a bytestream between two Jabber entities.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>rel</shortname><supersededby><spec>XEP-0065</spec></supersededby><last-revision><date>2003-09-30</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, the status of this specification has been changed to Retracted since it has been superseded by XEP-0065.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>42</number><title>Jabber OOB Broadcast Service (JOBS)</title><abstract>A protocol for enabling uni-directional multicast data transfers out of band.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>JOBS</shortname><supersededby><spec>XEP-0065</spec></supersededby><last-revision><date>2003-04-11</date><version>0.5</version><initials>psa</initials><remark>At the request of the author, changed status to Retracted.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>43</number><title>Jabber Database Access</title><abstract>Expose RDBM systems directly to the jabber network</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><last-revision><date>2003-10-20</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, changed status to Retracted.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>44</number><title>Full Namespace Support for XML Streams</title><abstract>A description of the use of namespaces within Jabber.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2002-08-26</date><version>0.1</version><initials>rn</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>45</number><title>Multi-User Chat</title><abstract>This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>muc</shortname><last-revision><date>2024-09-17</date><version>1.35.1</version><initials>gk</initials><remark>Add explicit error definition when non-owners attempt to use owner-specific functionality.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>46</number><title>DTCP</title><abstract>Direct TCP connection between two Jabber entities.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0065</spec></supersededby><last-revision><date>2003-04-11</date><version>0.8</version><initials>psa</initials><remark>At the request of the author, changed status to Retracted.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>47</number><title>In-Band Bytestreams</title><abstract>This specification defines an XMPP protocol extension that enables any two entities to establish a one-to-one bytestream between themselves, where the data is broken down into smaller chunks and transported in-band over XMPP.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>ibb</shortname><last-revision><date>2021-01-12</date><version>2.0.1</version><initials>sw</initials><remark>Fix incorrect max sequence number in the text; it was given as one less than two to the power of 15, but in reality it is one less than two to the power of 16, which is clear from the context).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>48</number><title>Bookmarks</title><abstract>This specification defines an XML data format for use by XMPP clients in storing bookmarks to mult-user chatrooms and web pages. The chatroom bookmarking function includes the ability to auto-join rooms on login.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>bookmarks</shortname><supersededby><spec>XEP-0402</spec></supersededby><last-revision><date>2020-08-04</date><version>1.2</version><initials>XEP Editor (jsc)</initials><remark>Deprecate in favour of XEP-0402</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>49</number><title>Private XML Storage</title><abstract>This specification provides canonical documentation of the 'jabber:iq:private' namespace currently in common usage.</abstract><type>Historical</type><status>Active</status><approver>Council</approver><shortname>iq-private</shortname><last-revision><date>2004-03-01</date><version>1.2</version><initials>psa</initials><remark>Corrected several errors in the text; specified security considerations.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>50</number><title>Ad-Hoc Commands</title><abstract>This document defines an XMPP protocol extension for advertising and executing application-specific commands, such as those related to a configuration workflow. Typically the commands contain data forms (XEP-0004) in order to structure the information exchange.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>commands</shortname><last-revision><date>2020-06-09</date><version>1.3.0</version><initials>kis</initials><remark>Clarify illegal uses of 'execute'.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>51</number><title>Connection Transfer</title><abstract>This specification defines an XMPP protocol extension that enables a server to redirect connections from one connection manager or server node to another.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>RFC6120</spec></supersededby><last-revision><date>2022-03-08</date><version>0.2.1</version><initials>egp</initials><remark>Obsolete because this feature has been merged into XMPP core, see RFC6120 section 4.9.3.19, which describes the &lt;see-other-host/&gt; stream error.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>52</number><title>File Transfer</title><abstract>A protocol for transferring a file between two Jabber IDs.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0095</spec><spec>XEP-0096</spec></supersededby><last-revision><date>2018-11-03</date><version>0.2.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>53</number><title>XMPP Registrar Function</title><abstract>This document defines the roles and processes of the XMPP Registrar function within the XMPP Standards Foundation.</abstract><type>Procedural</type><status>Active</status><approver>Board</approver><last-revision><date>2016-12-01</date><version>1.7</version><initials>psa</initials><remark>Modify registration status names to be consistent with IANA terminology (Provisional, Permanent, Historical).</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>54</number><title>vcard-temp</title><abstract>This specification provides canonical documentation of the vCard-XML format currently in use within the Jabber community.</abstract><type>Historical</type><status>Active</status><approver>Council</approver><shortname>vcard-temp</shortname><last-revision><date>2024-06-27</date><version>1.3.0</version><initials>gk</initials><remark>Updated error cases to be compatible with .</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>55</number><title>Jabber Search</title><abstract>This specification provides canonical documentation of the jabber:iq:search namespace currently in use within the Jabber community.</abstract><type>Historical</type><status>Active</status><approver>Council</approver><shortname>iq-search</shortname><last-revision><date>2009-09-15</date><version>1.3</version><initials>psa</initials><remark>Clarified that &lt;first/&gt; and &lt;last/&gt; elements in fact always represent given name and family name, respectively.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>56</number><title>Business Data Interchange</title><abstract>This document defines a way to transmit ebXML messages, ANSI X.11, EDIFACT/UN, and SAP iDoc over Jabber/XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.3.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>57</number><title>Extended Roster</title><abstract>This document defines a way to handle extended roster items.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><last-revision><date>2003-04-28</date><version>0.2</version><initials>psa</initials><remark>Changed the status to Retracted at the request of the author, since the proposed protocol was incompatible with XMPP and clients have begun using jabber:iq:private for this kind of functionality.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>58</number><title>Multi-User Text Editing</title><abstract>This document defines how several people may simultaneously edit text.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2002-11-12</date><version>0.1</version><initials>as</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>59</number><title>Result Set Management</title><abstract>This specification defines an XMPP protocol extension that enables an entity to page through and otherwise manage the receipt of large result sets. The protocol can be used in the context of any XMPP protocol that might send large result sets (such as service discovery, multi-user chat, and publish-subscribe). While the requesting entity in such an interaction can explicitly request the use of result set management, an indication that result set management is in use can also be proactively included by the responding entity when returning a limited result set in response to a query.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>rsm</shortname><last-revision><date>2006-09-20</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>60</number><title>Publish-Subscribe</title><abstract>This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an event notification (with or without payload) is then broadcasted to all entities that have subscribed to the node. Pubsub therefore adheres to the classic Observer design pattern and can serve as the foundation for a wide variety of applications, including news feeds, content syndication, rich presence, geolocation, workflow systems, network management systems, and any other application that requires event notifications.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>pubsub</shortname><last-revision><date>2023-09-07</date><version>1.26.0</version><initials>melvo</initials><remark>Add examples for publishing item without ID</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>61</number><title>Shared Notes</title><abstract>A simplistic mechanism for shared notes, modeled after common stickie note applications.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-09-30</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, changed the status of this document to Deferred pending development of an implementation; also changed the type to Informational.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>62</number><title>Packet Filtering</title><abstract>A framework for packet filtering rules.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2021-03-04</date><version>0.2.2</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>63</number><title>Basic Filtering Operations</title><abstract>A module that provides basic conditions and actions for packet filtering.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-09-30</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, changed the status of this document to Deferred pending development of an implementation; also changed the type to Informational.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>64</number><title>XPath Filtering</title><abstract>A module that provides an XPath matching condition for packet filtering.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-09-30</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, changed the status of this document to Deferred pending development of an implementation; also changed the type to Informational.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>65</number><title>SOCKS5 Bytestreams</title><abstract>This document defines an XMPP protocol extension for establishing an out-of-band bytestream between any two XMPP users, mainly for the purpose of file transfer. The bytestream can be either direct (peer-to-peer) or mediated (though a special-purpose proxy server). The typical transport protocol used is TCP, although UDP can optionally be supported as well.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>bytestreams</shortname><last-revision><date>2021-03-04</date><version>1.8.2</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>66</number><title>Out of Band Data</title><abstract>This specification defines two XMPP protocol extensions for communicating URIs, one for use in XMPP message stanzas and the other for use in a structured request-response interaction via XMPP IQ stanzas. Among other things, this enables one entity to inform another entity about a file that is available at an HTTP URL.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>oob</shortname><last-revision><date>2006-08-16</date><version>1.5</version><initials>psa</initials><remark>Per a vote of the Jabber Council, converted to Standards Track.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>67</number><title>Stock Data Transmission</title><abstract>This document specifies a data format for stock data distribution in the Jabber community.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-07-19</date><version>0.3</version><initials>uls</initials><remark>Added transmission in messages</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>68</number><title>Field Standardization for Data Forms</title><abstract>This document specifies how to standardize field variables used in the context of jabber:x:data forms.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><shortname>formtypes</shortname><last-revision><date>2020-05-05</date><version>1.3.0</version><initials>fs</initials><remark>Clarify field type handling of the FORM_TYPE field on submission forms.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>69</number><title>Compliance SIG</title><abstract>A proposal to form a SIG devoted to issues related to protocol compliance.</abstract><type>SIG Formation</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-01-29</date><version>0.1</version><initials>psa</initials><remark>Initial release</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>70</number><title>Verifying HTTP Requests via XMPP</title><abstract>This specification defines an XMPP protocol extension that enables verification of an HTTP request via XMPP.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>http-auth</shortname><last-revision><date>2016-12-09</date><version>1.0.1</version><initials>mp (XEP Editor: ssw)</initials><remark>Mention a plaintext fallback.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>71</number><title>XHTML-IM</title><abstract>This specification defines an XHTML 1.0 Integration Set for use in exchanging instant messages that contain lightweight text markup. The protocol enables an XMPP entity to format a message using a small range of commonly-used HTML elements, attributes, and style properties that are suitable for use in instant messaging. The protocol also excludes HTML constructs that may introduce malware and other vulnerabilities (such as scripts and objects) for improved security.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>xhtml-im</shortname><last-revision><date>2018-03-08</date><version>1.5.4</version><initials>XEP Editor (jwi)</initials><remark>Correction: Council voted to Deprecate, not Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>72</number><title>SOAP Over XMPP</title><abstract>This specification defines methods for transporting SOAP messages over XMPP. Although the protocol supports only the request-response message exchange pattern, the protocol is formally defined as a SOAP Protocol Binding in accordance with version 1.2 of the W3C SOAP specification. In addition, a WSDL definition is defined for the purpose of advertising the availability of this protocol binding.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>soap</shortname><last-revision><date>2022-03-22</date><version>1.0.1</version><initials>gl</initials><remark>Fix incorrect reference to sipub namespace.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>73</number><title>Basic IM Protocol Suite</title><abstract>This document defines a recommended suite of Jabber/XMPP protocols to be supported by basic instant messaging and presence applications. Note: This protocol suite has been obsoleted by XEP-0211 and XEP-0212.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0242</spec><spec>XEP-0243</spec></supersededby><last-revision><date>2021-03-04</date><version>1.2.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>74</number><title>Simple Access Control</title><abstract>A simple protocol for querying information for permissions.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>sac</shortname><last-revision><date>2003-10-20</date><version>0.2</version><initials>psa</initials><remark>At the request of the author, changed status to Retracted.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>75</number><title>Jabber Object Access Protocol (JOAP)</title><abstract>The Jabber Object Access Protocol, or JOAP, defines a mechanism for creating Jabber-accessible object servers, and manipulating objects provided by those servers. It is intended for development of business applications with Jabber.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-05-22</date><version>0.3</version><initials>esp</initials><remark>For consistency, renamed hyphenated elements
      'new-address' and 'return-type' to 'newAddress' and 'returnType'
      respectively. Added 'desc' element for human-readable
      descriptions to object servers and classes. Changed the
      'writeable' [sic] attribute to the more correct
      'writable'. Added experimental namespace recommendation in
      XMPP Registrar section.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>76</number><title>Malicious Stanzas</title><abstract>This document defines an XMPP protocol extension for flagging malicious stanzas.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><shortname>evil</shortname><last-revision><date>2019-10-09</date><version>1.0.1</version><initials>fs</initials><remark>Fix  example.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>77</number><title>In-Band Registration</title><abstract>This specification defines an XMPP protocol extension for in-band registration with XMPP-based instant messaging servers and other services hosted on an XMPP network (such as groupchat rooms and gateways to non-XMPP IM services). The protocol is extensible via use of data forms, thus enabling services to gather a wide range of information during the registration process. The protocol also supports in-band password changes and cancellation of an existing registration.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>iq-register</shortname><last-revision><date>2012-01-25</date><version>2.4</version><initials>psa</initials><remark>Defined service discovery support.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>78</number><title>Non-SASL Authentication</title><abstract>This document specifies a protocol for authentication with Jabber servers and services using the jabber:iq:auth namespace. Note Well: The protocol specified herein has been superseded in favor of SASL authentication as specified in RFC 3920 / RFC 6120, and is now obsolete.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>iq-auth</shortname><supersededby><spec>RFC 6120</spec></supersededby><last-revision><date>2008-10-29</date><version>2.5</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>79</number><title>Advanced Message Processing</title><abstract>This specification defines an XMPP protocol extension that enables entities to request, and servers to perform, advanced processing of XMPP message stanzas, including reliable data transport, time-sensitive delivery, and expiration of transient messages.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>amp</shortname><supersedes><spec>XEP-0023</spec></supersedes><last-revision><date>2005-11-30</date><version>1.2</version><initials>psa</initials><remark>Consolidated and generalized security considerations.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>80</number><title>User Location</title><abstract>This specification defines an XMPP protocol extension for communicating information about the current geographical or physical location of an entity.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>geoloc</shortname><last-revision><date>2015-12-01</date><version>1.9</version><initials>ls</initials><remark>Added &lt;altaccuracy/&gt; element.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>81</number><title>Jabber MIME Type</title><abstract>This document specifies a MIME type for launching a Jabber client as a helper application from most modern web browsers, and for completing basic use cases once the client is launched.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>mimetype</shortname><last-revision><date>2005-07-19</date><version>0.5</version><initials>psa</initials><remark>Retracted the proposal (again) in favor of draft-saintandre-xmpp-iri.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>82</number><title>XMPP Date and Time Profiles</title><abstract>This document specifies a standardization of ISO 8601 profiles and their lexical representation for use in XMPP protocol extensions.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2021-08-31</date><version>1.1.1</version><initials>@Yquas</initials><remark>Fix typos</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>83</number><title>Nested Roster Groups</title><abstract>This document defines an XMPP protocol extension that enables nested sub-groups to exist within the Jabber roster, while retaining backwards compatibility and ensuring that the roster remains usable by all clients.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><shortname>nestedgroups</shortname><last-revision><date>2004-10-11</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced to a status of Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>84</number><title>User Avatar</title><abstract>This document defines an XMPP protocol extension for exchanging user avatars, which are small images or icons associated with human users. The protocol specifies payload formats for both avatar metadata and the image data itself. The payload formats are typically transported using the personal eventing profile of XMPP publish-subscribe as specified in XEP-0163.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>avatar</shortname><supersedes><spec>XEP-0008</spec><spec>XEP-0153</spec></supersedes><last-revision><date>2019-09-20</date><version>1.1.4</version><initials>egp</initials><remark>Use xs:unsignedInt for bytes, the previous revision introduced xs:unsignedInteger which isn&#8217;t a valid XML Schema data type.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>85</number><title>Chat State Notifications</title><abstract>This document defines an XMPP protocol extension for communicating the status of a user in a chat session, thus indicating whether a chat partner is actively engaged in the chat, composing a message, temporarily paused, inactive, or gone. The protocol can be used in the context of a one-to-one chat session or a multi-user chat room.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>chatstates</shortname><supersedes><spec>XEP-0022</spec></supersedes><last-revision><date>2009-09-23</date><version>2.1</version><initials>psa</initials><remark>Clarified that any state change is allowed.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>86</number><title>Error Condition Mappings</title><abstract>A mapping to enable legacy entities to correctly handle errors from XMPP-aware entities.</abstract><type>Informational</type><status>Deprecated</status><approver>Council</approver><last-revision><date>2004-02-17</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>87</number><title>Stream Initiation</title><abstract>A common method to initiate a stream with meta information</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>si</shortname><supersededby><spec>XEP-0095</spec></supersededby><last-revision><date>2022-03-22</date><version>0.1.1</version><initials>gl</initials><remark>Fix incorrect URL to SI namespace.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>88</number><title>Client Webtabs</title><abstract>A protocol for displaying web-based tabs in clients.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><shortname>webtab</shortname><last-revision><date>2004-03-14</date><version>0.4</version><initials>red</initials><remark>Added Terminology section and associated alterations and added clarification about what the webtabs are.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>89</number><title>Generic Alerts</title><abstract>A protocol for generic alerts (similar to .NET Alerts service).</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-05-16</date><version>0.2</version><initials>red</initials><remark>Changed element from x to alert.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>90</number><title>Legacy Entity Time</title><abstract>This specification provides historical documentation of the legacy jabber:iq:time namespace, which has been deprecated in favor the urn:xmpp:time namespace defined in XEP-0202.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>iq-time</shortname><supersededby><spec>XEP-0202</spec></supersededby><last-revision><date>2009-05-27</date><version>1.2</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>91</number><title>Legacy Delayed Delivery</title><abstract>This specification provides historical documentation of the legacy jabber:x:delay namespace, which has been deprecated in favor the urn:xmpp:delay namespace defined in XEP-0203.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>x-delay</shortname><supersededby><spec>XEP-0203</spec></supersededby><last-revision><date>2009-05-27</date><version>1.4</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>92</number><title>Software Version</title><abstract>This specification defines an XMPP protocol extension for retrieving information about the software application associated with an XMPP entity. The protocol enables one entity to explicitly query another entity, where the response can include the name of the software application, the version of the software application, and the operating system on which the application is running.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>iq-version</shortname><last-revision><date>2007-02-15</date><version>1.1</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; recommended use of Entity Capabilities instead of Software Version when presence information is available; added proviso to security considerations regarding disclosure of operating system information; added section on Service Discovery.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>93</number><title>Roster Item Exchange</title><abstract>This specification provides canonical documentation of the jabber:x:roster namespace historically used within the Jabber community. NOTE WELL: This specification has been superseded by XEP-0144.</abstract><type>Historical</type><status>Deprecated</status><approver>Council</approver><shortname>x-roster</shortname><supersededby><spec>XEP-0144</spec></supersededby><last-revision><date>2005-08-26</date><version>1.2</version><initials>psa</initials><remark>Per advancement of XEP-0144 by the Jabber Council, changed status to Deprecated.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>94</number><title>Agent Information</title><abstract>This specification provides canonical documentation of the obsolete Agent Information namespace. Note: This document has been superseded by XEP-0030: Service Discovery.</abstract><type>Historical</type><status>Obsolete</status><approver>Council</approver><shortname>iq-agents</shortname><supersededby><spec>XEP-0030</spec></supersededby><last-revision><date>2003-10-08</date><version>0.3</version><initials>psa</initials><remark>Per a vote of the Jabber Council, changed status to Obsolete. The protocol described herein is accurately defined but actively deprecated in favor of Service Discovery (XEP-0030).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>95</number><title>Stream Initiation</title><abstract>This specification defines an XMPP protocol extension for initiating a data stream between any two XMPP entities. The protocol includes the ability to include metadata about the stream and provides a pluggable framework so that various profiles of stream initiation can be defined for particular use cases (such as file transfer).</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>si</shortname><supersededby><spec>XEP-0166</spec></supersededby><last-revision><date>2017-11-29</date><version>1.2</version><initials>XEP Editor (ssw)</initials><remark>Deprecated by vote of the council.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>96</number><title>SI File Transfer</title><abstract>This specification defines a profile of the XMPP stream initiation extension for transferring files between two entities. The protocol provides a modular framework that enables the exchange of information about the file to be transferred as well as the negotiation of parameters such as the transport to be used.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>si-filetransfer</shortname><supersededby><spec>XEP-0234</spec></supersededby><last-revision><date>2022-03-22</date><version>1.3.1</version><initials>gl</initials><remark>Fix incorrect reference to sipub namespace</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>97</number><title>iCal Envelope</title><abstract>A simple mechanism to transport iCal data over the jabber protocol</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>ice</shortname><last-revision><date>2003-06-10</date><version>0.1</version><initials>jk</initials><remark>Initial draft (jk).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>98</number><title>Enhanced Private XML Storage</title><abstract>Standardizes "private" XML data storage.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>private-xml</shortname><last-revision><date>2003-06-25</date><version>0.1</version><initials>iss</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>99</number><title>IQ Query Action Protocol</title><abstract>Standardizes behavior of actions for generic query behavior.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.1.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>100</number><title>Gateway Interaction</title><abstract>This document specifies best practices for interactions between Jabber clients and client proxy gateways to legacy IM services.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><shortname>gateway</shortname><last-revision><date>2005-10-05</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>101</number><title>HTTP Authentication using Jabber Tickets</title><abstract>This document defines a protocol for authenticating HTTP requests using Jabber Tickets.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.2.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>102</number><title>Security Extensions</title><abstract>Security extensions for Jabber/XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-06-25</date><version>0.1</version><initials>jls</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>103</number><title>URL Address Information</title><abstract>This document defines a structure for providing information about an Uniform Resource Locator (URL), and a protocol signaling retrieval states.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>url-data</shortname><last-revision><date>2018-11-03</date><version>0.4.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>104</number><title>HTTP Scheme for URL Data</title><abstract>This document provides a schema description for detailed information about HTTP URLs.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2020-12-30</date><version>0.3.1</version><initials>ps</initials><remark>Add missing 'http:' prefix in example elements</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>105</number><title>Tree Transfer Stream Initiation Profile</title><abstract>A profile describing metadata for transferring trees of files using stream inititation.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>si-treetransfer</shortname><last-revision><date>2018-11-03</date><version>0.3.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>106</number><title>JID Escaping</title><abstract>This specification defines a mechanism that enables the display in Jabber Identifiers (JIDs) of characters normally disallowed in localparts. Although these characters spaces, double quote, ampersand, single quote, forward slash, colon, less than, greater than, and at-sign cannot be included in XMPP localparts, JID Escaping provides a native XMPP escaping mechanism for these characters so that the displayed version of a Jabber Identifier can appear to include these characters. This mechanism can also be used to translate non-XMPP addreses into XMPP syntax, for example when gatewaying between XMPP and a non-XMPP communications technology such as email.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jid\20escaping</shortname><last-revision><date>2016-07-08</date><version>1.1.1</version><initials>ssw</initials><remark>Update references to the node identifier to localpart, replace stringprep references with PRECIS, and update JID RFC references.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>107</number><title>User Mood</title><abstract>This specification defines a payload format for communicating information about user moods, such as whether a person is currently happy, sad, angry, or annoyed. The payload format is typically transported using the personal eventing protocol, a profile of XMPP publish-subscribe specified in XEP-0163.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>mood</shortname><last-revision><date>2024-06-20</date><version>1.2.2</version><initials>XEP Editor (dg)</initials><remark>Fixed typo</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>108</number><title>User Activity</title><abstract>This specification defines a payload format for communicating information about user activities, such as whether a person is currently working, travelling, or relaxing. The payload format is typically transported using the personal eventing protocol, a profile of XMPP publish-subscribe specified in XEP-0163.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>activity</shortname><last-revision><date>2008-10-29</date><version>1.3</version><initials>psa</initials><remark>Allowed empty activity element to signify a pause in publishing; added undefined element to handle any unspecified activity; also added more activities: dancing, fishing, hiding, praying, smoking, thinking.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>109</number><title>Out-of-Office Messages</title><abstract>This document defines an XMPP protocol extension for communicating out-of-office status.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>ooo</shortname><last-revision><date>2022-03-22</date><version>0.3.2</version><initials>gl</initials><remark>Fix not well-formed XML in example.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>110</number><title>Generic Maps</title><abstract>A protocol for transport of generic maps (graphical displays of specific subsets of buddies).</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-07-28</date><version>0.1</version><initials>jk</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>111</number><title>A Transport for Initiating and Negotiating Sessions (TINS)</title><abstract>This document defined a SIP-compatible transport for initiating and negotiating sessions using SDP over XMPP.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>tins</shortname><supersededby><spec>XEP-0166</spec></supersededby><last-revision><date>2005-12-21</date><version>0.8</version><initials>psa/jjh</initials><remark>Retracted in favor of Jingle (XEP-0166).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>112</number><title>User Physical Location</title><abstract>This document defines a protocol for communicating information about the current physical location of a Jabber entity. NOTE WELL: The protocol defined herein has been folded into XEP-0080.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>physloc</shortname><supersededby><spec>XEP-0080</spec></supersededby><last-revision><date>2004-10-12</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>113</number><title>Simple Whiteboarding</title><abstract>A proposal for an extremely simple whiteboarding protocol over Jabber.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2003-09-07</date><version>0.2</version><initials>hji</initials><remark>Added optional stroke, stroke-width and id attributes to the path element; added move and delete elements; added remark on Coccinella protocol and tkabber to introduction; added explanation about text-drawing and clear-screen discussion to implementation notes.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>114</number><title>Jabber Component Protocol</title><abstract>This specification documents the existing protocol used for communication between servers and "external" components over the Jabber network.</abstract><type>Historical</type><status>Active</status><approver>Council</approver><shortname>component</shortname><last-revision><date>2012-01-25</date><version>1.6</version><initials>psa</initials><remark>Removed unnecessary and unimplemented requirement to escape predefined XML entities.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>115</number><title>Entity Capabilities</title><abstract>This document defines an XMPP protocol extension for broadcasting and dynamically discovering client, device, or generic entity capabilities. In order to minimize network impact, the transport mechanism is standard XMPP presence broadcast (thus forestalling the need for polling related to service discovery data), the capabilities information can be cached either within a session or across sessions, and the format has been kept as small as possible.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>caps</shortname><last-revision><date>2022-03-08</date><version>1.6.0</version><initials>ssw</initials><remark>Mention preimage attacks explicitly</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>116</number><title>Encrypted Session Negotiation</title><abstract>This document specifies an XMPP protocol extension for negotiating an end-to-end encrypted session.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.16</version><initials>ip</initials><remark>Split pubkey field into init_pubkey and resp_pubkey fields; modified namespaces to reflect XMPP Registrar procedures regarding URN issuance.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>117</number><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><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0213</spec><spec>XEP-0216</spec></supersededby><last-revision><date>2007-10-30</date><version>1.1</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete and referred implementors to XEP-0213 and XEP-0216.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>118</number><title>User Tune</title><abstract>This specification defines a payload format for communicating information about music to which a user is listening, including the title, track number, collection, performer, composer, length, and user rating. The payload format is typically transported using the personal eventing protocol, a profile of XMPP publish-subscribe specified in XEP-0163.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>tune</shortname><last-revision><date>2020-10-20</date><version>1.3.0</version><initials>mwb</initials><remark>Add further tags for non-pop music</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>119</number><title>Extended Presence Protocol Suite</title><abstract>This document specifies a set of XMPP extensions that provide support for extended presence information.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0163</spec></supersededby><last-revision><date>2006-08-08</date><version>0.8</version><initials>psa</initials><remark>Retracted: superseded by Personal Eventing via Pubsub (XEP-0163).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>120</number><title>Infobits</title><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>infobits</shortname><last-revision><date>2004-01-22</date><version>0.5</version><initials>psa</initials><remark>Clarified rationale for not using namespaces; added bundles; added dataype attribute for &lt;bit/&gt; elements; added Matt Miller as co-author.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>121</number><title>Dublin Core Infobits Mapping</title><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract><type>Informational</type><status>Retracted</status><approver>Council</approver><last-revision><date>2003-12-15</date><version>0.6</version><initials>psa</initials><remark>Confined proposal to Dublin Core only.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>122</number><title>Data Forms Validation</title><abstract>This specification defines a backwards-compatible extension to the XMPP Data Forms protocol that enables applications to specify additional validation guidelines related to a form, such as validation of standard XML datatypes, application-specific datatypes, value ranges, and regular expressions.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>xdata-validate</shortname><last-revision><date>2018-03-21</date><version>1.0.2</version><initials>fs</initials><remark>Remove text about element emptiness.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>123</number><title>Entity Metadata</title><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><last-revision><date>2003-12-16</date><version>0.3</version><initials>psa</initials><remark>Incorporated infobits changes and vCard infobit mappings; metadata about relationships to be moved to forthcoming specification.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>124</number><title>Bidirectional-streams Over Synchronous HTTP (BOSH)</title><abstract>This specification defines a transport protocol that emulates the semantics of a long-lived, bidirectional TCP connection between two entities (such as a client and a server) by efficiently using multiple synchronous HTTP request/response pairs without requiring the use of frequent polling or chunked responses.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>bosh</shortname><last-revision><date>2021-05-22</date><version>1.11.2</version><initials>mw</initials><remark>Fix incorrect attribute name in text (from vs. to)</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>125</number><title>vCard Infobits Mapping</title><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract><type>Informational</type><status>Retracted</status><approver>Council</approver><last-revision><date>2003-12-15</date><version>0.1</version><initials>psa</initials><remark>Initial version, split off from version 0.5 of XEP-0121 (with revisions to more clearly map vCard elements); further mapping and description required.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>126</number><title>Invisibility</title><abstract>This specification defines best practices regarding implementation of invisible presence by means of XMPP privacy lists.</abstract><type>Informational</type><status>Deprecated</status><approver>Council</approver><supersededby><spec>XEP-0186</spec></supersededby><last-revision><date>2005-08-19</date><version>1.1</version><initials>psa</initials><remark>Corrected order of presence and IQ stanzas to ensure proper processing by server.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>127</number><title>Common Alerting Protocol (CAP) Over XMPP</title><abstract>This document specifies a method for sending Common Alerting Protocol (CAP) data over XMPP.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2004-12-09</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>128</number><title>Service Discovery Extensions</title><abstract>This document specifies best practices for including extended information in Service Discovery results.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2019-07-30</date><version>1.0.1</version><initials>gdk</initials><remark>Remove now-incorrect informational statement about the likelihood of multiple forms in a single disco#info reply.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>129</number><title>WebDAV File Transfers</title><abstract>This document specifies a method for completing file transfers between XMPP entities using WebDAV.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-04-19</date><version>0.3</version><initials>psa</initials><remark>Corrected to reflect changes to XEP-0070; incorporated WedDAV feedback.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>130</number><title>Waiting Lists</title><abstract>This document defines an XMPP protocol extension that enables a user to add a non-IM user to a waiting list and be informed when the contact creates an IM account.</abstract><type>Historical</type><status>Deprecated</status><approver>Council</approver><shortname>waitinglist</shortname><last-revision><date>2021-03-04</date><version>1.4.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>131</number><title>Stanza Headers and Internet Metadata</title><abstract>This specification defines an XMPP protocol extension for representing non-address-related headers in an XML format that is appropriate for use in XMPP. While the protocol provides a flexible mechanism for representing many kinds of standard Internet metadata, a registry of values is defined to structure the possible range of headers, and the inital registration includes headers from email, HTTP, MIME, and SIP.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>shim</shortname><last-revision><date>2006-07-12</date><version>1.2</version><initials>psa</initials><remark>Added Urgency header from registry.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>132</number><title>Presence Obtained via Kinesthetic Excitation (POKE)</title><abstract>This document defines an XMPP protocol extension that enables probing for presence via physical rather than electronic means.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><shortname>poke</shortname><last-revision><date>2004-04-01</date><version>1.0</version><initials>psa</initials><remark>April Fools!</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>133</number><title>Service Administration</title><abstract>This document defines recommended best practices for service-level administration of servers and components using Ad-Hoc Commands.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><shortname>admin</shortname><last-revision><date>2024-09-01</date><version>1.3.1</version><initials>dc</initials><remark>Fixed typo in example for Get User Last Login Time</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>134</number><title>XMPP Design Guidelines</title><abstract>This document defines best practices for the intelligent design of Jabber protocols and other XMPP extensions.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2004-12-09</date><version>1.1</version><initials>psa</initials><remark>Revised text regarding recommended stanza sizes.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>135</number><title>File Sharing</title><abstract>This document specifies a simple extension to existing protocols for file sharing over Jabber/XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>files</shortname><last-revision><date>2004-06-04</date><version>0.1</version><initials>psa</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>136</number><title>Message Archiving</title><abstract>This document defines mechanisms and preferences for the server-side archiving and retrieval of XMPP messages.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>archive</shortname><supersededby><spec>XEP-0313</spec></supersededby><last-revision><date>2021-03-04</date><version>1.3.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>137</number><title>Publishing Stream Initiation Requests</title><abstract>This specification defines an XMPP protocol extension that enables an XMPP entity to advertise the fact that it is willing accept a particular Stream Initiation request. The protocol is used mainly to inform other entities that a particular file is available for transfer via the File Transfer protocol defined in XEP-0096.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>sipub</shortname><last-revision><date>2018-02-28</date><version>1.1</version><initials>XEP Editor (ssw)</initials><remark>Deprecated per a vote of the XMPP Council.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>138</number><title>Stream Compression</title><abstract>This document defines an XMPP protocol extension for negotiating compression of XML streams, especially in situations where standard TLS compression cannot be negotiated. The protocol provides a modular framework that can accommodate a wide range of compression algorithms; the ZLIB compression algorithm is mandatory-to-implement, but implementations may support other algorithms in addition.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>compress</shortname><last-revision><date>2022-02-10</date><version>2.1</version><initials>tjb</initials><remark>Obsolete due to security vulnerability.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>139</number><title>Security SIG</title><abstract>This document proposes the formation of a Special Interest Group devoted to the analysis of security threats related to Jabber technologies.</abstract><type>SIG Formation</type><status>Retracted</status><approver>Council</approver><last-revision><date>2004-09-15</date><version>0.2</version><initials>psa</initials><remark>Changed status to Retracted since it now appears unnecessary to form a SIG in order to complete this work; rather, it should be sufficient to write a XEP and solicit feedback from appropriate security experts before the Last Call. However, such a XEP should use the process described herein.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>140</number><title>Shared Groups</title><abstract>This document defines a protocol profile for centrally defined and administered roster groups; the protocol described herein has been retracted in favor of XEP-0144: Roster Item Exchange.</abstract><type>Informational</type><status>Retracted</status><approver>Council</approver><shortname>groups</shortname><supersededby><spec>XEP-0144</spec></supersededby><last-revision><date>2004-10-27</date><version>0.2</version><initials>psa</initials><remark>Retracted in favor of XEP-0144.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>141</number><title>Data Forms Layout</title><abstract>This specification defines a backwards-compatible extension to the XMPP Data Forms protocol that enables an application to specify form layouts, including the layout of form fields, sections within pages, and subsections within sections.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>xdata-layout</shortname><last-revision><date>2005-05-12</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>142</number><title>Workgroup Queues</title><abstract>This document defines an XMPP protocol extension that enables a user to communicate with a representative of an organization, department, or workgroup.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.3.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>143</number><title>Guidelines for Authors of XMPP Extension Protocols</title><abstract>This document provides information intended to assist authors of XMPP Extension Protocols.</abstract><type>Procedural</type><status>Active</status><approver>Council</approver><last-revision><date>2016-12-02</date><version>1.1.2</version><initials>psa</initials><remark>Reflect preference for GitHub pull requests to maintain existing XEPs; update terminology to refer to XMPP Extensions Editor team.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>144</number><title>Roster Item Exchange</title><abstract>This specification defines an XMPP protocol extension for exchanging contact list items, including the ability to suggest whether the item is to be added, deleted, or modified in the contact list of the recipient, as well as the suggested roster group for the item.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>rosterx</shortname><supersedes><spec>XEP-0093</spec></supersedes><last-revision><date>2017-11-28</date><version>1.1.1</version><initials>dtr (XEP Editor: jwi)</initials><remark>Fix JID example</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>145</number><title>Annotations</title><abstract>This document defines a protocol for making annotations about roster items and other entities.</abstract><type>Historical</type><status>Active</status><approver>Council</approver><shortname>rosternotes</shortname><last-revision><date>2006-03-23</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>146</number><title>Remote Controlling Clients</title><abstract>This document specifies recommended best practices for remote controlling clients using Ad-Hoc Commands.</abstract><type>Informational</type><status>Obsolete</status><approver>Council</approver><shortname>rc</shortname><last-revision><date>2017-11-07</date><version>1.1</version><initials>XEP Editor (ssw)</initials><remark>Per a vote of the XMPP Council, advanced to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>147</number><title>XMPP URI Scheme Query Components</title><abstract>This document defines a registry of query components to be used in the context of XMPP IRIs/URIs and also specifies an initial submission of values to that registry.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><shortname>querytypes</shortname><last-revision><date>2006-09-13</date><version>1.2</version><initials>psa</initials><remark>Removed probe action.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>148</number><title>Instant Messaging Intelligence Quotient (IM IQ)</title><abstract>This specification provides canonical documentation of the jabber:iq:iq namespace.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><shortname>iq-iq</shortname><last-revision><date>2022-11-03</date><version>1.1</version><initials>pep</initials><remark>Replace shtml link</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>149</number><title>Time Periods</title><abstract>This document defines a method to specify the valid time periods for states, events, and activities communicated via Jabber/XMPP protocols.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2006-01-24</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the Jabber Council, advanced status to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>150</number><title>Use of Entity Tags in XMPP Extensions</title><abstract>This document defines best practices for the use of Entity Tags in XMPP extensions.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2005-08-09</date><version>0.2</version><initials>psa</initials><remark>Added security considerations.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>151</number><title>Virtual Presence</title><abstract>This document proposes extensions to the Jabber groupchat protocol for virtual presence on Web pages.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2005-07-05</date><version>0.2</version><initials>hw</initials><remark>Simplified VPI file and rule syntax, basically omitting the rule/search/replace tags.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>152</number><title>Reachability Addresses</title><abstract>This document defines an XMPP protocol extension for communicating information about how an entity can be reached temporarily using methods other than the entity's normal JID.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>reach</shortname><last-revision><date>2014-02-25</date><version>1.0</version><initials>XEP Editor (mm)</initials><remark>Per a vote of the XMPP Council, advanced specification from Experimental to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>153</number><title>vCard-Based Avatars</title><abstract>This document provides historical documentation of a vCard-based protocol for exchanging user avatars.</abstract><type>Historical</type><status>Active</status><approver>Council</approver><shortname>vcard-avatar</shortname><last-revision><date>2024-06-10</date><version>1.1.1</version><initials>egp</initials><remark>XEP-0054 says &#8220;Email addresses MUST be contained in a &lt;USERID&gt; element&#8221;.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>154</number><title>User Profile</title><abstract>This document specifies how to represent and manage profile data about IM users and other XMPP entities using the XMPP Data Forms extension.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><supersedes><spec>XEP-0054</spec></supersedes><last-revision><date>2021-03-04</date><version>0.6.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>155</number><title>Stanza Session Negotiation</title><abstract>This specification defines a method for formally negotiating the exchange of XML stanzas between two XMPP entities. The method uses feature negotiation forms sent via XMPP message stanzas to enable session initiation between entities that do not share presence information or have knowledge of full JabberIDs and therefore is also suitable for use across gateways to SIP-based systems. A wide range of session parameters can be negotiated, including the use of end-to-end encryption, chat state notifications, XHTML-IM formatting, and message archiving.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>ssn</shortname><last-revision><date>2016-01-20</date><version>1.2</version><initials>XEP Editor (mam)</initials><remark>Update missing 'xmppsipim' reference to RFC 7572.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>156</number><title>Discovering Alternative XMPP Connection Methods</title><abstract>This document defines an XMPP Extension Protocol for discovering alternative methods of connecting to an XMPP server via Web Host Metadata Link format.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>alt-connections</shortname><last-revision><date>2022-02-10</date><version>1.4.0</version><initials>tjb</initials><remark>Remove DNS _xmppconnect method due to security vulnerability.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>157</number><title>Contact Addresses for XMPP Services</title><abstract>This document defines a method for specifying contact addresses related to an XMPP service.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2021-03-04</date><version>1.1.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>158</number><title>CAPTCHA Forms</title><abstract>This document specifies an XMPP protocol extension that entities may use to discover whether the sender of an XML stanza is a human user or a robot.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>captcha</shortname><last-revision><date>2019-11-07</date><version>1.0.1</version><initials>egp, mb</initials><remark>Use the correct FORM_TYPE for extended IBR, and use a proper MUC join as an example. Also fix typos.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>159</number><title>Spim-Blocking Control</title><abstract>This document defines an XMPP protocol extension that enables clients to control how their servers may block spim that is addressed to them. It specifies a default privacy list fall-through action.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2006-07-11</date><version>0.3</version><initials>psa</initials><remark>Updated to reflect move of privacy rules to XEP-0016; modified provisional namespaces to adhere to XMPP Registrar policies; completed editorial review.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>160</number><title>Best Practices for Handling Offline Messages</title><abstract>This document specifies best practices to be followed by Jabber/XMPP servers in handling messages sent to recipients who are offline.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><shortname>msgoffline</shortname><last-revision><date>2016-10-07</date><version>1.0.1</version><initials>egp</initials><remark>Use the correct namespace in the Service Discovery examples; fix some formatting.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>161</number><title>Abuse Reporting</title><abstract>This document specifies an XMPP protocol extension for reporting abusive XMPP stanzas.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><supersededby><spec>XEP-0268</spec></supersededby><last-revision><date>2007-05-06</date><version>0.4</version><initials>psa</initials><remark>Generalized text and protocol to handle all kinds of abuse and folded in content from XEP-0236.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>162</number><title>Best Practices for Roster and Subscription Management</title><abstract>This document specifies best practices for roster and subscription management in Jabber/XMPP clients.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2020-06-25</date><version>0.2.1</version><initials>ps</initials><remark>Fixed small typos</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>163</number><title>Personal Eventing Protocol</title><abstract>This specification defines semantics for using the XMPP publish-subscribe protocol to broadcast state change events associated with an instant messaging and presence account. This profile of pubsub therefore enables a standard XMPP user account to function as a virtual pubsub service, easing the discovery of syndicated data and event notifications associated with such an account.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>pep</shortname><last-revision><date>2022-02-16</date><version>1.2.2</version><initials>melvo</initials><remark>Add comma and fix typo</remark></last-revision><sig>Standards JIG</sig></xep><xep accepted="true"><number>164</number><title>vCard Filtering</title><abstract>This document specifies a mechanism for requesting specific sections of a vCard.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>vcard-temp-filter</shortname><last-revision><date>2005-11-16</date><version>0.1</version><initials>psa</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>165</number><title>Best Practices to Discourage JID Mimicking</title><abstract>This document recommends best practices to discourage mimicking of Jabber IDs.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-12-13</date><version>0.6</version><initials>psa</initials><remark>Added security consideration about storage of handle in the roster.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>166</number><title>Jingle</title><abstract>This specification defines an XMPP protocol extension for initiating and managing peer-to-peer media sessions between two XMPP entities in a way that is interoperable with existing Internet standards. The protocol provides a pluggable model that enables the core session management semantics (compatible with SIP) to be used for a wide variety of application types (e.g., voice chat, video chat, file transfer) and with a wide variety of transport methods (e.g., TCP, UDP, ICE, application-specific transports).</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle</shortname><supersedes><spec>XEP-0095</spec></supersedes><last-revision><date>2018-09-19</date><version>1.1.2</version><initials>egp</initials><remark>Add missing security-info in section&#160;5.1, forgotten in version&#160;0.35.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>167</number><title>Jingle RTP Sessions</title><abstract>This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle-rtp</shortname><last-revision><date>2022-09-26</date><version>1.2.2</version><initials>melvo</initials><remark>Specify attribute 'name' of 'mute' and 'unmute' elements as optional in schema</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>168</number><title>Resource Application Priority</title><abstract>This document defines an XMPP protocol extension to indicate the presence priority of XMPP resources for applications other than standard XMPP messaging.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-09-26</date><version>0.7</version><initials>psa</initials><remark>* More clearly defined the meaning of "application type".
* Modified namespaces to incorporate namespace versioning.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>169</number><title>Twas The Night Before Christmas (Jabber Version)</title><abstract>The classic Christmas poem annotated with XMPP protocols.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><last-revision><date>2021-03-04</date><version>1.1.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>170</number><title>Recommended Order of Stream Feature Negotiation</title><abstract>This document specifies a recommended order for negotiation of XMPP stream features.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2007-01-04</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced status to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>171</number><title>Language Translation</title><abstract>This specification defines an XMPP protocol extension for providing language translation facilities over XMPP. It supports human, machine, client-based, and server-based translations.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>langtrans</shortname><last-revision><date>2015-10-15</date><version>1.1.1</version><initials>XEP Editor (mam)</initials><remark>Corrected XML schema to note a number of constructs are optional not required (Christian Schudt).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>172</number><title>User Nickname</title><abstract>This specification defines a protocol for communicating user nicknames, either in XMPP presence subscription requests or in XMPP messages.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>nick</shortname><last-revision><date>2012-03-21</date><version>1.1</version><initials>psa</initials><remark>Based on implementation and deployment experience, discouraged use in Multi-User Chat; also removed text about Waiting Lists because of lack of deployment.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>173</number><title>Pubsub Subscription Storage</title><abstract>This document defines an XMPP protocol extension for storing subscriptions to Pubsub nodes.</abstract><type>Historical</type><status>Deferred</status><approver>Council</approver><shortname>pubsubs</shortname><last-revision><date>2006-02-09</date><version>0.1</version><initials>psa</initials><remark>Initial version; changed title to Pubsub Subscription Storage; changed namespace to storage:pubsubs for consistency with other storage XEPs.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>174</number><title>Serverless Messaging</title><abstract>This specification defines how to communicate over local or wide-area networks using the principles of zero-configuration networking for endpoint discovery and the syntax of XML streams and XMPP messaging for real-time communication. This method uses DNS-based Service Discovery and Multicast DNS to discover entities that support the protocol, including their IP addresses and preferred ports. Any two entities can then negotiate a serverless connection using XML streams in order to exchange XMPP message and IQ stanzas.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>linklocal</shortname><last-revision><date>2018-02-08</date><version>2.0.1</version><initials>cs</initials><remark>Fix incorrect STARTTLS examples.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>175</number><title>Best Practices for Use of SASL ANONYMOUS</title><abstract>This document specifies best practices for use of the SASL ANONYMOUS mechanism in the context of client authentication with an XMPP server.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2009-09-30</date><version>1.2</version><initials>psa</initials><remark>Provided more detailed recommendations regarding usage restrictions for anonymous users, including the concept of different deployment types; added note about the account/anonymous service discovery identity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>176</number><title>Jingle ICE-UDP Transport Method</title><abstract>This specification defines a Jingle transport method that results in sending media data using raw datagram associations via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology, which provides robust NAT traversal for media traffic.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle-ice-udp</shortname><last-revision><date>2021-03-04</date><version>1.1.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>177</number><title>Jingle Raw UDP Transport Method</title><abstract>This specification defines a Jingle transport method that results in sending media data using raw datagram associations via the User Datagram Protocol (UDP). This simple transport method does not provide NAT traversal, and the ICE-UDP transport method should be used if NAT traversal is required.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle-raw-udp</shortname><last-revision><date>2020-12-10</date><version>1.1.1</version><initials>egp</initials><remark>Made type optional in the schema (it&#8217;s a MAY in section 4.2), unlike in XEP-0176.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>178</number><title>Best Practices for Use of SASL EXTERNAL with Certificates</title><abstract>This document specifies best practices for XMPP usage of the SASL EXTERNAL mechanism in the context of PKIX certificates.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2020-08-19</date><version>1.2</version><initials>@woj-tek</initials><remark>Add fallback to dialback if EXTERNAL authentication fails due to practical experience.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>179</number><title>Jingle IAX Transport Method</title><abstract>This document defines a Jingle transport method that results in using the Inter-Asterisk eXchange protocol (IAX) for the final communication.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jingle-iax</shortname><last-revision><date>2006-03-23</date><version>0.2</version><initials>psa</initials><remark>Recommended use of IAX-native methods for DTMF.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>180</number><title>Jingle Video via RTP</title><abstract>Note: This specification has been retracted in favor of XEP-0167, which now consolidates both audio and video chat via RTP and therefore contains the content originally published in this specification; please refer to XEP-0167 for the most up-to-date definition of XMPP video chat. This specification defines a Jingle application type for negotiating a video chat or other video session. The application type uses the Real-time Transport Protocol (RTP) for the underlying media exchange and provides a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0167</spec></supersededby><last-revision><date>2008-06-04</date><version>0.13</version><initials>psa</initials><remark>Retracted in favor of XEP-0167, which now consolidates both audio and video chat via RTP and therefore contains the content originally published in this specification.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>181</number><title>Jingle DTMF</title><abstract>This specification defines an XML format for encapsulating Dual Tone Multi-Frequency (DTMF) events in informational messages sent within the context of Jingle audio sessions, e.g. to be used in the context of Interactive Voice Response (IVR) systems. Note well that this format is not to be used in the context of RTP sessions, where native RTP methods are to be used instead.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-10-02</date><version>0.12</version><initials>psa</initials><remark>Corrected definitions and schema to make it clear that the code attribute contains one and only one character representing a DTMF tone.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>182</number><title>Application-Specific Error Conditions</title><abstract>This document defines a registry of application-specific error conditions.</abstract><type>Procedural</type><status>Active</status><approver>Council</approver><shortname>errors</shortname><last-revision><date>2008-03-05</date><version>1.1</version><initials>psa</initials><remark>Changed namespace from http://jabber.org/protocol/errors to urn:xmpp:errors.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>183</number><title>Jingle Telepathy Transport</title><abstract>This document defines a telepathic transport method for establishing Extra-Sensory Perception (ESP) streams.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><shortname>telepathy</shortname><last-revision><date>2006-04-01</date><version>1.0</version><initials>psa</initials><remark>April Fools!</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>184</number><title>Message Delivery Receipts</title><abstract>This specification defines an XMPP protocol extension for message delivery receipts, whereby the sender of a message can request notification that the message has been delivered to a client controlled by the intended recipient.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>receipts</shortname><supersedes><spec>XEP-0022 (in part)</spec></supersedes><last-revision><date>2018-08-02</date><version>1.4.0</version><initials>egp</initials><remark>Make the 'id' attribute required, this extension makes no sense otherwise.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>185</number><title>Dialback Key Generation and Validation</title><abstract>This document provides a recommended method for generating and validating the keys used in the XMPP server dialback protocol.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2007-02-15</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>186</number><title>Invisible Command</title><abstract>This document specifies an XMPP protocol extension for user invisibility.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>invisible</shortname><supersedes><spec>XEP-0018</spec><spec>XEP-0126</spec></supersedes><last-revision><date>2018-12-06</date><version>0.14.0</version><initials>XEP Editor (jsc)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig><lastcall>2017-12-21</lastcall></xep><xep accepted="true"><number>187</number><title>Offline Encrypted Sessions</title><abstract>This document specifies an end-to-end encryption protocol for offline XMPP communication sessions.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.5</version><initials>ip/psa</initials><remark>Added reference to Requirements for Encrypted Sessions; modified namespaces to reflect XMPP Registrar procedures regarding URN issuance.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>188</number><title>Cryptographic Design of Encrypted Sessions</title><abstract>This document describes the cryptographic design that underpins the XMPP protocol extensions Encrypted Session Negotiation, Offline Encrypted Sessions and Stanza Encryption.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.6</version><initials>ip</initials><remark>SIGMA-R negotiates both isPKA and isPKB fields</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>189</number><title>Public Key Publishing</title><abstract>This specification defines a method by which an entity can publish its public keys over XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2010-07-15</date><version>0.14</version><initials>psa</initials><remark>Defined an RSA-specific child element of the pubkey element to contain the modulus, public exponent, and fingerprint directly (rather than a DER-encoded format that depends on ASN.1); specified that the public exponent should be 65537; clarified the fingerprint generation method and updated all of the fingerprint formats to enable hash agility; incremented namespaces from version 1 to version 2.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>190</number><title>Best Practice for Closing Idle Streams</title><abstract>This document specifies a best practice for closing an XML stream that is perceived to be idle.</abstract><type>Informational</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>RFC 6120</spec></supersededby><last-revision><date>2012-03-06</date><version>1.1</version><initials>psa</initials><remark>Changed status to Obsolete because it is superseded by RFC 6120.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>191</number><title>Blocking Command</title><abstract>This document specifies an XMPP protocol extension for communications blocking.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>blocking</shortname><supersedes><spec>XEP-0016</spec></supersedes><last-revision><date>2015-03-12</date><version>1.3</version><initials>ssw</initials><remark>Clarify that arbitrary JIDs may be blocked to match current usage of this spec in the wild.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>192</number><title>Proposed Stream Feature Improvements</title><abstract>This document proposes improvements to the XML stream features definition for inclusion in the specification that supersedes RFC 3920.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>RFC 6120</spec></supersededby><last-revision><date>2012-02-08</date><version>1.2</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status from Deprecated to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>193</number><title>Proposed Resource Binding Improvements</title><abstract>This document proposes improvements to the definition of resource binding for inclusion in the specification that supersedes RFC 3920.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><last-revision><date>2012-02-08</date><version>1.2</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status from Deprecated to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>194</number><title>User Chatting</title><abstract>This specification defines an XMPP protocol extension for communicating information about the chatrooms a user visits.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-09-25</date><version>0.3</version><initials>psa</initials><remark>Modified namespace in accordance with protocol versioning policies.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>195</number><title>User Browsing</title><abstract>This document defines an XMPP protocol extension for communicating information about the web pages a user visits.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-09-25</date><version>0.3</version><initials>psa</initials><remark>Modified namespace in accordance with protocol versioning policies.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>196</number><title>User Gaming</title><abstract>This document defines an XMPP protocol extension for communicating information about the games a user plays.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-09-25</date><version>0.3</version><initials>psa</initials><remark>Modified namespace in accordance with protocol versioning policies.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>197</number><title>User Viewing</title><abstract>This document defines an XMPP protocol extension for communicating information about the television shows, movies, or other videos that a user watches.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-09-25</date><version>0.3</version><initials>psa</initials><remark>Modified namespace in accordance with protocol versioning policies.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>198</number><title>Stream Management</title><abstract>This specification defines an XMPP protocol extension for active management of an XML stream between two XMPP entities, including features for stanza acknowledgements and stream resumption.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>sm</shortname><last-revision><date>2024-09-24</date><version>1.6.2</version><initials>gk</initials><remark>Clarify server enabling stream management without requested resume functionality.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>199</number><title>XMPP Ping</title><abstract>This specification defines an XMPP protocol extension for sending application-level pings over XML streams. Such pings can be sent from a client to a server, from one server to another, or end-to-end.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>ping</shortname><last-revision><date>2019-03-26</date><version>2.0.1</version><initials>o01eg</initials><remark>Fix incorrect IQ type in example (result =&gt; error)</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>200</number><title>Stanza Encryption</title><abstract>This document specifies an XMPP protocol extension for session-based stanza encryption.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.2</version><initials>ip</initials><remark>Added reference to Simplified Encrypted Session Negotiation; modified namespaces to reflect XMPP Registrar procedures regarding URN issuance.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>201</number><title>Best Practices for Message Threads</title><abstract>This specification defines recommended handling of XMPP message threads.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2010-11-29</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Active.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>202</number><title>Entity Time</title><abstract>This specification defines an XMPP protocol extension for communicating the local time of an entity, including the time in UTC according to the entity as well as the offset from UTC. The time format itself conforms to the dateTime profile of ISO 8601 defined in XEP-0082.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>time</shortname><supersedes><spec>XEP-0090</spec></supersedes><last-revision><date>2009-09-11</date><version>2.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification from Draft to Final.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>203</number><title>Delayed Delivery</title><abstract>This specification defines an XMPP protocol extension for communicating the fact that an XML stanza has been delivered with a delay, for example because a message has been stored on a server while the intended recipient was offline or because a message is contained in the history of a multi-user chat room.</abstract><type>Standards Track</type><status>Final</status><approver>Council</approver><shortname>delay</shortname><supersedes><spec>XEP-0091</spec></supersedes><last-revision><date>2009-09-15</date><version>2.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification from Draft to Final; also addressed a security concern about forged timestamps that was provided during the Call for Experience.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>204</number><title>Collaborative Data Objects</title><abstract>This document specifies an XMPP protocol extension that supports the exchange of structured data objects.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-01-17</date><version>0.1</version><initials>psa</initials><remark>Initial published version; modified namespaces to adhere to XSF policy.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>205</number><title>Best Practices to Discourage Denial of Service Attacks</title><abstract>This document recommends a number of practices that can help discourage denial of service attacks on XMPP-based networks.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2021-03-04</date><version>1.0.2</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>206</number><title>XMPP Over BOSH</title><abstract>This specification defines how the Bidirectional-streams Over Synchronous HTTP (BOSH) technology can be used to transport XMPP stanzas. The result is an HTTP binding for XMPP communications that is useful in situations where a device or client is unable to maintain a long-lived TCP connection to an XMPP server.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>xbosh</shortname><last-revision><date>2014-04-09</date><version>1.4</version><initials>ls/wt</initials><remark>Incorporated patches from community review.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>207</number><title>XMPP Eventing via Pubsub</title><abstract>This document specifies semantics for using the XMPP publish-subscribe protocol to handle generic XMPP events (including presence, one-to-one messaging, and groupchat).</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><last-revision><date>2007-04-01</date><version>1.0</version><initials>psa</initials><remark>April Fools!</remark></last-revision><sig>Standards JIG</sig></xep><xep accepted="true"><number>208</number><title>Bootstrapping Implementation of Jingle</title><abstract>This document provides guidelines to XMPP client developers for bootstrapping implementation of Jingle technologies.</abstract><type>Informational</type><status>Retracted</status><approver>Council</approver><last-revision><date>2009-01-06</date><version>0.4</version><initials>psa</initials><remark>Retracted because unnecessary given the wide implementation of Jingle.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>209</number><title>Metacontacts</title><abstract>This document specifies an XMPP protocol extension for defining metacontacts and grouping member JIDs.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-04-10</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards JIG</sig></xep><xep accepted="true"><number>210</number><title>Requirements for Encrypted Sessions</title><abstract>This document describes the requirements for an XMPP end-to-end encrypted session protocol.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.2</version><initials>ip</initials><remark>Clarified introduction.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>211</number><title>XMPP Basic Client 2008</title><abstract>This document defines the XMPP Basic Client 2008 compliance level.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0242</spec></supersededby><last-revision><date>2007-07-11</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>212</number><title>XMPP Basic Server 2008</title><abstract>This document defines the XMPP Basic Server 2008 compliance level.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0243</spec></supersededby><last-revision><date>2007-07-11</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>213</number><title>XMPP Intermediate IM Client 2008</title><abstract>This document defines the XMPP Intermediate IM Client 2008 compliance level.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0242</spec></supersededby><last-revision><date>2007-07-11</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>214</number><title>File Repository and Sharing</title><abstract>While a protocol has been described for initiating a file transfer from one user to another, there is not yet a defined way for users to designate a set of files as available for retrieval by other users of their choosing. This extension defines a common syntax for this purpose which is based on PubSub Collections.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2022-03-22</date><version>0.3.1</version><initials>gl</initials><remark>Fix incorrect reference to sipub namespace.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>215</number><title>External Service Discovery</title><abstract>This document specifies an XMPP protocol extension for discovering services external to the XMPP network.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>extdisco</shortname><last-revision><date>2022-08-23</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Accept as Stable as per Council Vote from 2022-08-03.</remark></last-revision><sig>Standards</sig><lastcall>2022-07-27</lastcall></xep><xep accepted="true"><number>216</number><title>XMPP Intermediate IM Server 2008</title><abstract>This document defines the XMPP Intermedate IM Server 2008 compliance level.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>XEP-0243</spec></supersededby><last-revision><date>2007-07-11</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>217</number><title>Simplified Encrypted Session Negotiation</title><abstract>This document specifies a minimal subset of the Encrypted Session Negotiation protocol sufficent for negotiating an end-to-end encrypted session.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.1</version><initials>psa</initials><remark>Initial published version; modified namespaces to reflect XMPP Registrar procedures regarding URN issuance.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>218</number><title>Bootstrapping Implementation of Encrypted Sessions</title><abstract>This document provides guidelines to client and library developers for bootstrapping implementation of the encrypted sessions technology.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-05-30</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>219</number><title>Hop Check</title><abstract>This document defines an XMPP protocol extension that enables an entity to check the security of client-to-server and server-to-server hops between it and another entity. Note: This specification has been retracted by the author because the problem is not compelling and a real solution would be too complicated.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><last-revision><date>2008-06-12</date><version>0.3</version><initials>psa</initials><remark>Retracted by the author because the problem is not compelling and a real solution would be too complicated.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>220</number><title>Server Dialback</title><abstract>This specification defines the Server Dialback protocol, which is used between XMPP servers to provide identity verification. Server Dialback uses the Domain Name System (DNS) as the basis for verifying identity; the basic approach is that when a receiving server accepts a server-to-server connection from an initiating server, it does not process XMPP stanzas over the connection until it has verified the initiating server's identity. Additionally, the protocol is used to negotiate whether the receiving server is accepting stanzas for the target domain. Although Server Dialback does not provide strong authentication and is subject to DNS poisoning attacks, it has effectively prevented most address spoofing on the XMPP network since its development in the year 2000.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>dialback</shortname><last-revision><date>2015-03-12</date><version>1.1.1</version><initials>ssw</initials><remark>Update DNA framework reference to RFC 7712.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>221</number><title>Data Forms Media Element</title><abstract>This specification defines an XMPP protocol extension for including media data in XEP-0004 data forms.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>media-element</shortname><last-revision><date>2008-09-03</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced status to Draft; concurrently, the XMPP Registrar issued the urn:xmpp:media-element namespace.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>222</number><title>Persistent Storage of Public Data via PubSub</title><abstract>This specification defines best practices for using the XMPP publish-subscribe extension to persistently store semi-public data objects such as public keys and personal profiles.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2008-09-08</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Active.</remark></last-revision><sig>Standards JIG</sig></xep><xep accepted="true"><number>223</number><title>Persistent Storage of Private Data via PubSub</title><abstract>This specification defines best practices for using the XMPP publish-subscribe extension to persistently store private information such as bookmarks and client configuration options.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2023-03-23</date><version>1.1.1</version><initials>ka</initials><remark>Add notes about checking event origin (in reaction to CVE-2023-28686).</remark></last-revision><sig>Standards JIG</sig></xep><xep accepted="true"><number>224</number><title>Attention</title><abstract>This document defines an XMPP protocol extension for getting the attention of another user.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>attention</shortname><last-revision><date>2008-11-13</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>225</number><title>Component Connections</title><abstract>This document specifies a standards-track XMPP protocol extension that enables server components to connect to XMPP servers.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>component</shortname><last-revision><date>2008-10-06</date><version>0.2</version><initials>psa</initials><remark>Modified namespace to incorporate namespace versioning; clarified that the value of the &lt;hostname/&gt; element can be either &lt;domain&gt; or &lt;domain/resource&gt;.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>226</number><title>Message Stanza Profiles</title><abstract>This document specifies best practices for generating and handling extended content in XMPP message stanzas.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><shortname>profiles</shortname><last-revision><date>2008-11-05</date><version>0.3</version><initials>psa</initials><remark>For consistency, defined Metadata Profile; specified that the registrar shall create a registry for message stanza profiles.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>227</number><title>Portable Import/Export Format for XMPP-IM Servers</title><abstract>This document specifies a file format for importing and exporting user data to and from XMPP-IM servers.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>pie</shortname><last-revision><date>2021-06-02</date><version>1.1</version><initials>mw</initials><remark>Discourage use of 'password', provide a way to include SCRAM credentials, PEP nodes and message archives.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>228</number><title>Requirements for Shared Editing</title><abstract>This document defines requirements for the design of XMPP-based shared editing protocols.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2007-08-22</date><version>0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>229</number><title>Stream Compression with LZW</title><abstract>This document specifies how to use the LZW algorithm in XML stream compression.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><last-revision><date>2022-02-10</date><version>1.1</version><initials>tjb</initials><remark>Obsolete due to security vulnerability.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>230</number><title>Service Discovery Notifications</title><abstract>This specification defines a method for requesting and receiving notifications regarding XMPP service discovery items.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-09-08</date><version>0.1.2</version><initials>fs</initials><remark>Add forgotten node attribute in example 2.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>231</number><title>Bits of Binary</title><abstract>This specification defines an XMPP protocol extension for including or referring to small bits of binary data in an XML stanza.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>bob</shortname><last-revision><date>2022-07-25</date><version>1.1</version><initials>ssw</initials><remark>Mention where to get textual names of hash functions.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>232</number><title>Software Information</title><abstract>This document specifies an extended data format whereby XMPP service discovery responses can include detailed information about the software application that powers a given XMPP entity for includion in service discovery responses.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-02-26</date><version>0.3</version><initials>psa</initials><remark>Per Last Call feedback, removed icons for presence states; redefined the icon field to use media element per XEP-0221.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>233</number><title>XMPP Server Registration for use with Kerberos V5</title><abstract>This specification defines the Kerberos principal name of an XMPP server. It also details a method by which a connecting client can determine this Kerberos principal name when authenticating using the "GSSAPI" SASL mechanism.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>kerberos5</shortname><last-revision><date>2017-03-16</date><version>1.0.0</version><initials>XEP Editor (ssw)</initials><remark>Move to draft by order of the XMPP Council.</remark></last-revision><sig>Standards</sig><lastcall>2017-03-01</lastcall></xep><xep accepted="true"><number>234</number><title>Jingle File Transfer</title><abstract>This specification defines a Jingle application type for transferring a file from one entity to another. The protocol provides a modular framework that enables the exchange of information about the file to be transferred as well as the negotiation of parameters such as the transport to be used.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jingle-ft</shortname><supersedes><spec>XEP-0096</spec></supersedes><last-revision><date>2019-06-19</date><version>0.19.1</version><initials>ri0n</initials><remark>Fix use of hash elements from XEP&#8212;0300.</remark></last-revision><sig>Standards</sig><lastcall>2017-12-12</lastcall></xep><xep accepted="true"><number>235</number><title>OAuth Over XMPP</title><abstract>This specification defines an XMPP extension for delegating access to protected resources over XMPP, using the OAuth protocol.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-03-24</date><version>0.7</version><initials>psa</initials><remark>Changed protocol namespace from urn:xmpp:tmp:oauth to urn:xmpp:oauth:0 to conform to XMPP Registrar policies; clarified protocol flow and error handling; corrected examples.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>236</number><title>Abuse Reporting</title><abstract>This specification defines an XMPP protocol extension for reporting abusive traffic sent over an XMPP network. Note: This specification has been retracted in favor of XEP-0161, which now contains the content originally published in this specification.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><last-revision><date>2008-05-09</date><version>0.2</version><initials>psa</initials><remark>Retracted in favor of XEP-0161, which now contains the content originally published in this specification.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>237</number><title>Roster Versioning</title><abstract>This specification defines a proposed modification to the XMPP roster protocol that enables versioning of rosters such that the server will not send the roster to the client if the roster has not been modified, thus saving bandwidth during session establishment.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersededby><spec>RFC 6121</spec></supersededby><last-revision><date>2012-02-08</date><version>1.3</version><initials>psa</initials><remark>Per a vote of the XMPP Council, changed status to Obsolete since roster versioning was folded into RFC 6121.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>238</number><title>XMPP Protocol Flows for Inter-Domain Federation</title><abstract>This specification provides detailed protocol flows for the establishment of communication between domains that provide XMPP services, including permutations for a wide variety of possible federation policies.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-03-31</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>239</number><title>Binary XMPP</title><abstract>This specification defines Binary XMPP, an obviously superior representation of the Extensible Messaging and Presence Protocol (XMPP).</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><last-revision><date>2008-04-01</date><version>1.0</version><initials>pm/psa/ff</initials><remark>April Fools!</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>240</number><title>Auto-Discovery of JabberIDs</title><abstract>This specification defines a recommended best practice for linking to JabberIDs from documents hosted on the World Wide Web.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-04-30</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>241</number><title>Encryption of Archived Messages</title><abstract>This specification defines methods for encrypting messages that are archived at an XMPP server.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-04-30</date><version>0.1</version><initials>psa</initials><remark>Initial version, split off from XEP-0136 per XMPP Council consensus.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>242</number><title>XMPP Client Compliance 2009</title><abstract>This document defines XMPP client compliance levels for 2009.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersedes><spec>XEP-0211</spec><spec>XEP-0213</spec></supersedes><supersededby><spec>XEP-0270</spec></supersededby><last-revision><date>2008-09-08</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>243</number><title>XMPP Server Compliance 2009</title><abstract>This document defines XMPP server compliance levels for 2009.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersedes><spec>XEP-0212</spec><spec>XEP-0216</spec></supersedes><supersededby><spec>XEP-0270</spec></supersededby><last-revision><date>2008-09-08</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>244</number><title>IO Data</title><abstract>This specification defines an XMPP protocol extension for handling the input to and output from a remote entity.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-06-18</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>245</number><title>The /me Command</title><abstract>This specification defines recommended handling of the /me command in XMPP instant messaging clients.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2009-01-21</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Active and changed type from Historical to Informational.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>246</number><title>End-to-End XML Streams</title><abstract>This specification defines methods for communicating via end-to-end XML streams over a logical or physical connection that provides a reliable transport between two endpoints.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2016-01-20</date><version>0.1.1</version><initials>XEP Editor (mam)</initials><remark>Updated missing 'ice-tcp' reference to RFC 6544.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>247</number><title>Jingle XML Streams</title><abstract>This specification defines a Jingle application type for establishing direct or mediated XML streams between two entities over any streaming transport. This technology thus enables two entities to establish a trusted connection for end-to-end encryption or for bypassing server limits on large volumes of XMPP traffic.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-02-20</date><version>0.2</version><initials>dm/psa</initials><remark>Adjusted text and examples to reflect Jingle-XTLS, Jingle-IBB, and Jingle-S5B; moved stream security to Jingle-XTLS; moved basic stream setup from XEP-0246 to this document; changed examples to use Jingle-IBB as the transport; clarified stream opening and closing as well as session termination.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>248</number><title>PubSub Collection Nodes</title><abstract>This specification defines the nature and handling of collection nodes in the XMPP publish-subscribe extension.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2021-08-03</date><version>0.3.0</version><initials>rm</initials><remark>Revert change from version 0.2.1 which changed meta-data to metadata in wire protocol. That was an unintended breaking change which has now been reverted.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>249</number><title>Direct MUC Invitations</title><abstract>This specification defines a method for inviting a contact to a multi-user chat room directly, instead of sending the invitation through the chat room.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>x-conference</shortname><last-revision><date>2011-09-22</date><version>1.2</version><initials>psa</initials><remark>Added continue and thread attributes for feature parity with mediated invitations when converting a one-to-one chat to a groupchat.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>250</number><title>C2C Authentication Using TLS</title><abstract>This document describes how to negotiate TLS extensions when using TLS for end-to-end XML streams between two clients. It covers X.509 certificates with an without CA, the use of OpenPGP, Shared Remote Passwords (SRP) and how to use one extension to bootstrap a trust relationship.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-09-08</date><version>0.2</version><initials>dm</initials><remark>Use keyinfo from version 0.8 of XEP-0189.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>251</number><title>Jingle Session Transfer</title><abstract>This specification defines an extension to XMPP Jingle for transferring a session (such as a voice call) from one person to another.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-10-05</date><version>0.2</version><initials>psa</initials><remark>Updated examples; added reference to RFC 5359; added security considerations regarding unattended transfer.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>252</number><title>BOSH Script Syntax</title><abstract>This specification provides historical documentation regarding the "alternative script syntax" first defined in Version 1.6 of XEP-0124.</abstract><type>Historical</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-10-31</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>253</number><title>PubSub Chaining</title><abstract>This specification defines a method for chaining pubsub nodes together, resulting in lightweight repeaters for pubsub notifications.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-11-18</date><version>0.2</version><initials>psa</initials><remark>Specifed protocol flow for the chained subscription.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>254</number><title>PubSub Queueing</title><abstract>This specification defines an extension to XMPP publish-subscribe for queueing information at a node.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2008-11-13</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>255</number><title>Location Query</title><abstract>This specification defines an XMPP protocol extension for querying a compliant server or service for information about the geographical or physical location of an entity.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.6.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>256</number><title>Last Activity in Presence</title><abstract>This specification defines a way to use the Last Activity extension in XMPP presence notifications.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><supersededby><spec>XEP-0319</spec></supersededby><last-revision><date>2009-09-15</date><version>1.1</version><initials>psa</initials><remark>Added use case for initial presence.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>257</number><title>Client Certificate Management for SASL EXTERNAL</title><abstract>This specification defines a method to manage client certificates that can be used with SASL External to allow clients to log in without a password.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-07-18</date><version>0.3</version><initials>tpa</initials><remark>* Removed the dependency on .
* Placed the certificate data directly in the &lt;append/&gt; element.
* Clarified up the usage of the certificate's name.
* Increased the version to 'urn:xmpp:saslcert:1'.
* Added a section on discovering support.
* Added the possibility for the server to send a list of currently used certificates.
* Updated the relation with  to match the current version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>258</number><title>Security Labels in XMPP</title><abstract>This document describes the use of security labels in XMPP. The document specifies how security label metadata is carried in XMPP, when this metadata should or should not be provided, and how the metadata is to be processed.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>sec-label</shortname><last-revision><date>2018-11-03</date><version>1.1.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>259</number><title>Message Mine-ing</title><abstract>In servers that deliver messages intended for the bare JID to all resources, the resource that claims a conversation notifies all of the other resources of that claim.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>mine</shortname><last-revision><date>2009-01-21</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>260</number><title>Jingle SOCKS5 Bytestreams Transport Method</title><abstract>This specification defines a Jingle transport method that results in sending data via the SOCKS5 Bytestreams (S5B) protocol defined in XEP-0065. Essentially this transport method reuses XEP-0065 semantics for sending the data and defines native Jingle methods for starting and ending an S5B session.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle-s5b</shortname><last-revision><date>2018-05-15</date><version>1.0.3</version><initials>fs</initials><remark>Replace broken link using archive.org</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>261</number><title>Jingle In-Band Bytestreams Transport Method</title><abstract>This specification defines a Jingle transport method that results in sending data via the In-Band Bytestreams (IBB) protocol defined in XEP-0047. Essentially this transport method reuses XEP-0047 semantics for sending the data and defines native Jingle methods for starting and ending an IBB session.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle-ibb</shortname><last-revision><date>2011-09-23</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification from Experimental to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>262</number><title>Use of ZRTP in Jingle RTP Sessions</title><abstract>This specification defines how to use ZRTP (RFC 6189) in the Jingle application type for the Real-time Transport Protocol (RTP) as a way to negotiate media path key agreement for secure RTP in one-to-one media sessions.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>jingle-zrtp</shortname><last-revision><date>2011-06-15</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced specification to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>263</number><title>ECO-XMPP</title><abstract>This specification defines best practices and protocol modifications that will reduce the energy consumption of XMPP systems and thereby help to save the planet.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><shortname>eco-xmpp</shortname><last-revision><date>2009-04-01</date><version>1.0</version><initials>psa/ff</initials><remark>April Fools!</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>264</number><title>Jingle Content Thumbnails</title><abstract>This specification defines a way for a client to supply a preview image for Jingle content.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>thumbs</shortname><last-revision><date>2024-07-24</date><version>0.4.2</version><initials>egp</initials><remark>Restrict 'width' and 'height' to the 0..65535 range, instead of being unbounded integers.  This is in accordance to XEP-0084 and XEP-0221 for instance.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>265</number><title>Out-of-Band Stream Data</title><abstract>This specification defines how to send parts of an XML stream over a direct connection between peers. This allows to send large stanzas or binary data without blocking the XML stream for other stanzas.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-04-02</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>266</number><title>Codecs for Jingle Audio</title><abstract>This document describes implementation considerations related to audio codecs for use in Jingle RTP sessions.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2013-03-01</date><version>1.1.0-rc.1</version><initials>psa</initials><remark>Updated to reflect standardization of the Opus codec; changed client conformance to also recommend (but not require) support for Opus.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>267</number><title>Server Buddies</title><abstract>This specification defines a convention for presence subscriptions between XMPP servers.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-05-29</date><version>0.5</version><initials>psa</initials><remark>Corrected several examples and points in the text.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>268</number><title>Incident Handling</title><abstract>This specification defines methods for incident reporting among XMPP server deployments using the IODEF format produced by the IETF's INCH Working Group.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-05-29</date><version>0.6</version><initials>psa</initials><remark>Aligned document with the IETF guidelines for defining extensions to IODEF; defined several more IODEF NodeRole categories; added schema for the JID element; noted that the JID element might be moved to a separate specification.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>269</number><title>Jingle Early Media</title><abstract>This specification describes methods for exchanging early media in the context of Jingle RTP sessions.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-05-19</date><version>0.1</version><initials>dc/psa</initials><remark>Initial version, copied from XEP-0167.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>270</number><title>XMPP Compliance Suites 2010</title><abstract>This document defines XMPP protocol compliance levels for 2010.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersedes><spec>XEP-0242</spec><spec>XEP-0243</spec></supersedes><supersededby><spec>XEP-0302</spec></supersededby><last-revision><date>2017-01-28</date><version>1.1</version><initials>ssw</initials><remark>Per a vote of the XMPP Council, move specification from Draft to Obsolete.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>271</number><title>XMPP Nodes</title><abstract>This specification more clearly defines the nature of nodes as used in the Service Discovery and Publish-Subscribe extensions to the Extensible Messaging and Presence Protocol (XMPP).</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2009-06-26</date><version>0.1</version><initials>psa</initials><remark>Initial published version; per Council discussion changed local to localpart.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>272</number><title>Multiparty Jingle (Muji)</title><abstract>This specification defines an XMPP protocol extension for initiating and managing multiparty voice and video conferences within an XMPP MUC</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>muji</shortname><last-revision><date>2024-08-21</date><version>0.2.0</version><initials>lmw</initials><remark>* Send Jingle IQs to real JID
* Define how to use with XEP-0482
* Adjust namespace</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>273</number><title>Stanza Interception and Filtering Technology (SIFT)</title><abstract>This specification defines an XMPP protocol extension that enables a client to exercise control over the XML stanzas it will receive from the server by instructing the server to intercept and filter inbound stanzas.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>sift</shortname><last-revision><date>2011-06-27</date><version>0.4</version><initials>psa</initials><remark>Made it clear that presence means presence notifications; added support for subscription-related presence stanzas; described payload matching in greater detail; added use case for allowing only core XMPP child elements; increased protocol version number from 1 to 2.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>274</number><title>Design Considerations for Digital Signatures in XMPP</title><abstract>This document discusses considerations for the design of Digital Signatures in XMPP, including use cases and requirements. The document also discusses various ways XML Digital Signatures could be used in XMPP.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.4.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>275</number><title>Entity Reputation</title><abstract>This specification defines an XMPP protocol extension for communicating the reputation of any entity on the network.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>reputation</shortname><last-revision><date>2021-03-04</date><version>0.2.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>276</number><title>Presence Decloaking</title><abstract>This specification defines an XMPP protocol extension that enables a user to send directed presence with a request for the target to also share presence information for the duration of a communications session.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-07-13</date><version>0.3</version><initials>psa</initials><remark>Tweaked the security considerations.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>277</number><title>Microblogging over XMPP</title><abstract>This specification defines a method for microblogging over XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>microblog</shortname><last-revision><date>2022-02-15</date><version>0.6.5</version><initials>gh/@Yuubi-san</initials><remark>Fix incorrect double-escaping of entities in examples</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>278</number><title>Jingle Relay Nodes</title><abstract>This documents specifies how Jingle Clients can interact with Jingle Relay Nodes Services and how XMPP entities can provide, search and list available Jingle Relay Nodes.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jinglenodes</shortname><last-revision><date>2021-03-04</date><version>0.4.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>279</number><title>Server IP Check</title><abstract>This specification defines a simple XMPP extension that enables a client to discover its external IP address.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>sic</shortname><last-revision><date>2013-04-17</date><version>0.2</version><initials>psa</initials><remark>Modified XML format so server can return port as well as IP address; incremented protocol version from 0 to 1.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>280</number><title>Message Carbons</title><abstract>In order to keep all IM clients for a user engaged in a conversation, outbound messages are carbon-copied to all interested resources.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>carbons</shortname><supersedes><spec>XEP-0259</spec></supersedes><last-revision><date>2021-12-26</date><version>1.0.1</version><initials>egp</initials><remark>Fix indentation in examples.</remark></last-revision><sig>Standards</sig><lastcall>2021-04-06</lastcall></xep><xep accepted="true"><number>281</number><title>DMUC1: Distributed Multi-User Chat</title><abstract>This document defines methods for distributing Multi-User Chat (MUC) rooms across multiple chat services.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><supersededby><spec>XEP-0289</spec></supersededby><last-revision><date>2010-07-20</date><version>0.2</version><initials>psa</initials><remark>Added protocol flows for finding and joining shadow rooms, thus removing dependency on communication with firsthost; changed examples to mimic XEP-0045.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>282</number><title>DMUC2: Distributed MUC</title><abstract>Multi-User Chats, distributed over several nodes in the XMPP network, using a primary/replica architecture</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2021-03-04</date><version>0.1.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>283</number><title>Moved</title><abstract>This document defines an XMPP protocol extension that enables a user to inform its contacts about a change in JID.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>moved</shortname><last-revision><date>2021-07-20</date><version>0.2.0</version><initials>mw</initials><remark>Re-write the flow with a more focused approach.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>284</number><title>Shared XML Editing</title><abstract>This specification defines a protocol that enables two or more endpoints to collaboratively edit an XML object. The protocol is intended for use mainly over the Extensible Messaging and Presence Protocol (XMPP), either by existing instant messaging clients or by specialized editing clients. However, the protocol could also be used over a direct TCP connection rather than over XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2021-03-04</date><version>0.1.3</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>285</number><title>Encapsulating Digital Signatures in XMPP</title><abstract>This document provides a technical specification for Encapsulating Digital Signatures in the Extensible Messaging and Presence Protocol (XMPP).</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-01-12</date><version>0.3</version><initials>kdz</initials><remark>Change title, and clarify in text, that this is an encapulating digital
	signature approach, an alternative to the encapulated digitial signatures proposal.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>286</number><title>Mobile Considerations on LTE Networks</title><abstract>This document provides background information for XMPP implementors concerned with mobile devices operating on an LTE cellular network.</abstract><type>Informational</type><status>Active</status><approver>Council</approver><last-revision><date>2018-01-25</date><version>1.0.0</version><initials>XEP Editor (jwi)</initials><remark>Advance to Active as per Council vote on 2018-01-10.</remark></last-revision><sig>Standards</sig><lastcall>2017-11-15</lastcall></xep><xep accepted="true"><number>287</number><title>Spim Markers and Reports</title><abstract>This document defines an XMPP protocol extension that enables XMPP entities to interact with spim filters by marking unsolicited or suspicious XMPP stanzas.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2010-10-04</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>288</number><title>Bidirectional Server-to-Server Connections</title><abstract>This specification defines a protocol for using server-to-server connections in a bidirectional way such that stanzas are sent and received on the same TCP connection.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>bidi</shortname><last-revision><date>2016-10-17</date><version>1.0.1</version><initials>ssw</initials><remark>Fix syntax highlighting and tweak example formatting.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>289</number><title>Federated MUC for Constrained Environments</title><abstract>This document provides a protocol for federating MUC rooms together in order to reduce the effects of constrained network (e.g. unreliability, severely limited bandwidth) on the room occupants.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>FMUC</shortname><supersedes><spec>XEP-0281</spec></supersedes><last-revision><date>2021-03-04</date><version>0.2.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>290</number><title>Encapsulated Digital Signatures in XMPP</title><abstract>This document provides a technical specification for Encapsulated Digital Signatures in the Extensible Messaging and Presence Protocol (XMPP).</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-01-28</date><version>0.2</version><initials>kdz</initials><remark>Merge manifest and schema-desc objects.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>291</number><title>Service Delegation</title><abstract>This specification defines an approach for users to delegate certain services (e.g. pubsub) to alternative JIDs.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-01-26</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>292</number><title>vCard4 Over XMPP</title><abstract>This document specifies an XMPP extension for use of the vCard4 XML format in XMPP systems, with the intent of obsoleting the vcard-temp format.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><supersedes><spec>XEP-0054</spec></supersedes><last-revision><date>2023-03-14</date><version>0.12.0</version><initials>spw</initials><remark>Removes raw-IQ mode and specifies the reuse of PEP</remark></last-revision><sig>Standards</sig><lastcall>2019-02-19</lastcall></xep><xep accepted="true"><number>293</number><title>Jingle RTP Feedback Negotiation</title><abstract>This specification defines an XMPP extension to negotiate the use of the Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF) with Jingle RTP sessions</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2022-08-26</date><version>1.0.2</version><initials>melvo</initials><remark>Fix attribute name of 'parameter' element as specified by XML schema</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>294</number><title>Jingle RTP Header Extensions Negotiation</title><abstract>This specification defines an XMPP extension to negotiate the use of the use of RTP Header Extension as defined by RFC 8285 with Jingle RTP sessions</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2022-08-27</date><version>1.1.2</version><initials>melvo</initials><remark>Fix example description and attribute name of 'parameter' element as specified by XML schema</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>295</number><title>JSON Encodings for XMPP</title><abstract>This specification defines an alternative JSON encoding for XMPP stanzas and other elements.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><supersededby><spec>XEP-0335</spec></supersededby><last-revision><date>2011-04-01</date><version>1.0</version><initials>ks, mw</initials><remark>April Fools!</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>296</number><title>Best Practices for Resource Locking</title><abstract>This document specifies best practices to be followed by Jabber/XMPP clients about when to lock into, and unlock away from, resources.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-08-18</date><version>0.2</version><initials>mam</initials><remark>Expanded intro with a short problem description; moved chat states considerations to their own section; tightened requirement regarding a message from different resource from MAY to SHOULD; loosened requirement regarding a message with 'gone' from MUST to SHOULD; added missing but required sections</remark></last-revision><sig>Standards</sig><lastcall>2011-08-05</lastcall></xep><xep accepted="true"><number>297</number><title>Stanza Forwarding</title><abstract>This document defines a protocol to forward a stanza from one entity to another.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>forward</shortname><last-revision><date>2013-10-02</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced status to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>298</number><title>Delivering Conference Information to Jingle Participants (Coin)</title><abstract>This specification defines an XMPP extension for tightly coupled conference calls. It allows users who participate in multiparty Jingle calls via a focus agent (mixer) to retrieve information and receive notifications about the state of the call and the other participants. This extension is also meant to provide a straightforward way of connecting SIP and XMPP clients to the same conference room.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>coin</shortname><last-revision><date>2015-07-02</date><version>0.2</version><initials>sic</initials><remark>Correcting errors in grammar and examples; aligning closer to dependent specifications.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>299</number><title>Codecs for Jingle Video</title><abstract>This document describes implementation considerations related to video codecs for use in Jingle RTP sessions.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-06-12</date><version>0.1</version><initials>psa</initials><remark>Initial published version, split from XEP-0266.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>300</number><title>Use of Cryptographic Hash Functions in XMPP</title><abstract>This document provides a common wire format for the transport of cryptographic hash function references and hash function values in XMPP protocol extensions.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>hashes</shortname><last-revision><date>2019-11-13</date><version>1.0.0</version><initials>mb</initials><remark>Advance to Draft as per 2019-09-19 Council vote</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>301</number><title>In-Band Real Time Text</title><abstract>This is a specification for real-time text transmitted in-band over an XMPP session. Real-time text is text transmitted instantly while it is being typed or created.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>rtt</shortname><last-revision><date>2013-10-08</date><version>1.0</version><initials>psa</initials><remark>Per a vote of the XMPP Council, advanced status to Draft.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>302</number><title>XMPP Compliance Suites 2012</title><abstract>This document defines XMPP protocol compliance levels for 2012.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><supersedes><spec>XEP-0270</spec></supersedes><supersededby><spec>XEP-0375</spec></supersededby><last-revision><date>2011-07-21</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>303</number><title>Commenting</title><abstract>This specification defines a method for commenting.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-07-28</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>304</number><title>Whitespace Keepalive Negotiation</title><abstract>This specification defines a method for negotiating how to send keepalives in XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2011-08-18</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>305</number><title>XMPP Quickstart</title><abstract>This document defines methods for speeding the process of connecting or reconnecting to an XMPP server.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2013-03-01</date><version>0.3</version><initials>psa</initials><remark>Clarified the text in several places.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>306</number><title>Extensible Status Conditions for Multi-User Chat</title><abstract>This document defines an extensible format for status conditions in Multi-User Chat, similar to the error format used in the core of XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2016-06-07</date><version>0.2.1</version><initials>mp (XEP Editor: ssw)</initials><remark>Fix broken example XML.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>307</number><title>Unique Room Names for Multi-User Chat</title><abstract>This specification defines an XMPP protocol extension for requesting a unique room ID from a multi-user chat service.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>muc-unique</shortname><last-revision><date>2011-11-10</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>308</number><title>Last Message Correction</title><abstract>This specification defines a method for indicating that a message is a correction of the last sent message.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>message-correct</shortname><last-revision><date>2022-05-17</date><version>1.2.1</version><initials>gh/deuill</initials><remark>Fix disco#info example to use correct addresses.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>309</number><title>Service Directories</title><abstract>This specification shows how to combine and extend a number of existing XMPP protocols for improved sharing of information about XMPP servers.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-05-29</date><version>0.3</version><initials>psa</initials><remark>Corrected a number of details in the text, examples, and XMPP Registrar considerations; removed an extraneous section that is better contained in XEP-0267.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>310</number><title>Presence State Annotations</title><abstract>This document provides a protocol using which a server is able to provide information to clients indicating that previously received presence data may be stale.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>PSA</shortname><last-revision><date>2012-01-10</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>311</number><title>MUC Fast Reconnect</title><abstract>This document provides a protocol that can be used for limiting the amount of presence history needed when rejoining a MUC room.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>MFR</shortname><last-revision><date>2012-01-25</date><version>0.1</version><initials>psa</initials><remark>Version approved for publication by the XMPP Council.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>312</number><title>PubSub Since</title><abstract>This specification defines a publish-subscribe feature that enables a subscriber to automatically receive pubsub and PEP notifications since the last logout time of a specific resource.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-05-29</date><version>0.3</version><initials>psa</initials><remark>Corrected namespace to use namespace versioning; tweaked some of the delivery rules.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>313</number><title>Message Archive Management</title><abstract>This document defines a protocol to query and control an archive of messages stored on a server.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>mam</shortname><supersedes><spec>XEP-0136</spec></supersedes><last-revision><date>2024-09-18</date><version>1.1.2</version><initials>egp</initials><remark>* Fix JID and affiliation of the first two witches in the MUC example.
* Fix duplicated 'id' in MUC example.
* Fix indentation in examples.</remark></last-revision><sig>Standards</sig><lastcall>2021-03-30</lastcall></xep><xep accepted="true"><number>314</number><title>Security Labels in PubSub</title><abstract>This specification defines an extension to XEP-0258 (Security Labels) to allow for the use of security labels in XEP-0060 (Publish-Subscribe). This document describes how security label metadata can be applied to the various elements within Publish-Subscribe, including nodes and items.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2012-07-27</date><version>0.1</version><initials>psa</initials><remark>Initial published version.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>315</number><title>Data Forms XML Element</title><abstract>This specification defines an XMPP protocol extension for including XML-data in XEP-0004 data forms.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>xml-element</shortname><last-revision><date>2019-06-19</date><version>0.1.1</version><initials>fs</initials><remark>Fix shortname and section heading to avoid collision with XEP-0221</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>316</number><title>MUC Eventing Protocol</title><abstract>This specification defines semantics for using the XMPP publish-subscribe protocol to broadcast state change events associated with a Multi-User Chat (MUC) room. This profile of pubsub therefore enables a chatroom to function as a virtual pubsub service, easing the discovery of syndicated data and event notifications associated with such a room.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>mep</shortname><last-revision><date>2013-01-03</date><version>0.1</version><initials>psa</initials><remark>Initial published version approved for publication by the XMPP Council.</remark></last-revision><sig>Standards JIG</sig></xep><xep accepted="true"><number>317</number><title>Hats</title><abstract>This specification defines a more extensible model for roles and affiliations in Multi-User Chat rooms.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2023-06-28</date><version>0.2.0</version><initials>mw</initials><remark>Select a syntax for hats.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>318</number><title>Best Practices for Client Initiated Presence Probes</title><abstract>This specification defines a way to determine the time when a XMPP entity has last changed its presence. Using client initiated presence probes the current presence of subscribed XMPP users can be requested. In addition a protocol to request the uptime of servers and components is defined herein.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><shortname>last-presence</shortname><supersedes><spec>XEP-0012</spec></supersedes><last-revision><date>2013-08-06</date><version>0.2</version><initials>tobias</initials><remark>Fix issues raised in XMPP Council meeting.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>319</number><title>Last User Interaction in Presence</title><abstract>This specification defines a way to communicate time of last user interaction with her system using XMPP presence notifications.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>idle</shortname><supersedes><spec>XEP-0256</spec></supersedes><last-revision><date>2017-07-17</date><version>1.0.2</version><initials>egp</initials><remark>Make the schema more precise about a date being a xs:dateTime.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>320</number><title>Use of DTLS-SRTP in Jingle Sessions</title><abstract>This specification defines how to use DTLS-SRTP (RFC 5763) in the Jingle application type for the Real-time Transport Protocol (RTP) as a way to negotiate media path key agreement for secure RTP in one-to-one media sessions.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2020-05-26</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Move to Draft as per Council vote from 2020-05-20.</remark></last-revision><sig>Standards</sig><lastcall>2020-05-19</lastcall></xep><xep accepted="true"><number>321</number><title>Remote Roster Management</title><abstract>This document defines a way remote entities may manage user's roster to provide a simple way to keep rosters in sync.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.1.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>322</number><title>Efficient XML Interchange (EXI) Format</title><abstract>This specification describes how EXI compression can be used in XMPP networks.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>exi</shortname><last-revision><date>2018-01-25</date><version>0.6.0</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>323</number><title>Internet of Things - Sensor Data</title><abstract>Note: This specification has been retracted by the author; new implementations are not recommended. This specification provides the common framework for sensor data interchange over XMPP networks.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>sensor-data</shortname><last-revision><date>2017-05-20</date><version>0.6</version><initials>XEP Editor: ssw</initials><remark>Mark XEP as retracted by the author.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>324</number><title>Internet of Things - Provisioning</title><abstract>Note: This specification has been retracted by the author; new implementations are not recommended. This specification describes an architecture for efficient provisioning of services, access rights and user privileges in for the Internet of Things, where communication between Things is done using the XMPP protocol.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>sensor-network-provisioning</shortname><last-revision><date>2021-03-04</date><version>0.5.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>325</number><title>Internet of Things - Control</title><abstract>Note: This specification has been retracted by the author; new implementations are not recommended. This specification describes how to control devices or actuators in an XMPP-based sensor network.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>sensor-network-control</shortname><last-revision><date>2021-03-04</date><version>0.5.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>326</number><title>Internet of Things - Concentrators</title><abstract>Note: This specification has been retracted by the author; new implementations are not recommended. This specification describes how to manage and get information from concentrators of devices over XMPP networks.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>sensor-network-concentrators</shortname><last-revision><date>2017-05-20</date><version>0.4</version><initials>XEP Editor: ssw</initials><remark>Mark XEP as retracted by the author.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>327</number><title>Rayo</title><abstract>This specification defines an XMPP protocol extension for the third-party control of telephone calls and other similar media sessions. The protocol includes support for session management/signaling, as well as advanced media resources such as speech recognizers, speech synthesizers and audio/video recorders. The protocol serves a different purpose from that of first-party protocols such as Jingle or SIP, and is compatible with those protocols.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.8.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>328</number><title>JID Preparation and Validation Service</title><abstract>This specification defines a way for an XMPP entity to request another entity to prepare and validate a given JID.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jid-prep</shortname><last-revision><date>2019-12-16</date><version>0.2.1</version><initials>nv</initials><remark>Typographical fix.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>329</number><title>File Information Sharing</title><abstract>This document specifies a simple extension to existing protocols that allows an entity to request information about files.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>fis</shortname><supersedes><spec>XEP-0135</spec></supersedes><last-revision><date>2020-06-14</date><version>0.4.1</version><initials>fs</initials><remark>Fix example 7, remove superfluous 'node' attribute</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>330</number><title>Pubsub Subscription</title><abstract>This specification describe a method that allow a user to share a list of nodes on which it is Pubsub registered</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2013-06-11</date><version>0.1</version><initials>psa</initials><remark>Initial published version approved by the XMPP Council.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>331</number><title>Data Forms - Color Field Types</title><abstract>This specification defines how to publish fields in data forms that take color values. Color values are best edited using a color picker dialog, rather than manual input.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>color-parameter</shortname><last-revision><date>2015-11-09</date><version>0.3</version><initials>pw</initials><remark>Updated contact information.
Updated example JIDs to example.org</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>332</number><title>HTTP over XMPP transport</title><abstract>This specification defines how XMPP can be used to transport HTTP communication over peer-to-peer networks.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2020-03-31</date><version>0.5.1</version><initials>@sonnyp</initials><remark>Fix spelling error</remark></last-revision><sig>Standards</sig><lastcall>2014-10-21</lastcall></xep><xep accepted="true"><number>333</number><title>Displayed Markers</title><abstract>This specification introduces a method to let the sender, or multiple participants in a group chat, know that a client has displayed messages up to a certain point.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2024-04-17</date><version>1.0.0</version><initials>XEP Editor (dg)</initials><remark>Accept as Stable as per Council Vote from 2024-04-17.</remark></last-revision><sig>Standards</sig><lastcall>2024-04-08</lastcall></xep><xep accepted="true"><number>334</number><title>Message Processing Hints</title><abstract>This document defines a way to include hints to entities routing or receiving a message.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>hints</shortname><last-revision><date>2024-04-17</date><version>1.0.0</version><initials>XEP Editor (dg)</initials><remark>Accept as Stable as per Council Vote from 2024-04-17</remark></last-revision><sig>Standards</sig><lastcall>2024-04-08</lastcall></xep><xep accepted="true"><number>335</number><title>JSON Containers</title><abstract>This specification defines an element to be used for encapsulating JSON data in XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-09-26</date><version>0.1.1</version><initials>pep</initials><remark>Fix XEP number in schema description</remark></last-revision><sig>Standards</sig><lastcall>2019-02-19</lastcall></xep><xep accepted="true"><number>336</number><title>Data Forms - Dynamic Forms</title><abstract>This specification provides extensions to the data forms model defined in previous XEPs that permit enhanced end-user interaction and a better user experience. These extensions permit forms to react on user input by permitting the addition, updating or removal of fields in the form and server-side validation of fields. The extension also defines new states making it possible to display disabled controls, controls with undefined values or error messages, while still being backwards compatible with the existing data form model with available extensions.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>dynamic-forms</shortname><last-revision><date>2015-11-09</date><version>0.2</version><initials>pw</initials><remark>Updated contact information.
Updated example JIDs to example.org</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>337</number><title>Event Logging over XMPP</title><abstract>This specification provides a common framework for sending events to event logs over XMPP networks.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>eventlogging</shortname><last-revision><date>2017-09-11</date><version>0.3</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>338</number><title>Jingle Grouping Framework</title><abstract>This specification provides an XML mapping for translating the RFC 5888 SDP Grouping Framework to Jingle</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2020-07-21</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Advance to Draft as per Council vote from 2020-07-01</remark></last-revision><sig>Standards</sig><lastcall>2020-06-30</lastcall></xep><xep accepted="true"><number>339</number><title>Source-Specific Media Attributes in Jingle</title><abstract>This specification provides an XML mapping for translating the RFC 5766 Source-Specific Media Attributes from SDP to Jingle</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2021-10-23</date><version>1.0.1</version><initials>egp</initials><remark>Add a XML Schema, and fix an example lacking a namespace.</remark></last-revision><sig>Standards</sig><lastcall>2020-05-19</lastcall></xep><xep accepted="true"><number>340</number><title>COnferences with LIghtweight BRIdging (COLIBRI)</title><abstract>This specification defines an XMPP extension that allows real-time communications clients to discover and interact with conference bridges that provide conference mixing or relaying capabilities.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>colibri</shortname><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>341</number><title>Rayo CPA</title><abstract>This specification defines an extension to the Rayo protocol (XEP-0327) to provide provision for performing Call Progress Analysis on a call under the control of a Rayo client.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>342</number><title>Rayo Fax</title><abstract>This specification defines an extension to the Rayo protocol (XEP-0327) to provide provision for sending and receiving faxcimilies via a call under the control of a Rayo client.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2018-11-03</date><version>0.3.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>343</number><title>Signaling WebRTC datachannels in Jingle</title><abstract>This specification defines how to use the ICE-UDP Jingle transport method to send media data using WebRTC DataChannels, so technically uses DTLS/SCTP on top of the Interactive Connectivity Establishment (ICE) methodology, which provides robust NAT traversal for media traffic.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jingle-webrtc-datachannels</shortname><last-revision><date>2020-03-20</date><version>0.3.1</version><initials>ri0n</initials><remark>Fix attribute name (xmlns) in example</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>344</number><title>Impact of TLS and DNSSEC on Dialback</title><abstract>This specification provides documentation how Server Dialback is used together with Transport Layer Security, and discusses how the security considerations of Dialback are changed by the introduction of TLS and/or DNSSEC.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.4</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>345</number><title>Form of Membership Applications</title><abstract>This specification outlines the form and mandatory content of membership applications.</abstract><type>Procedural</type><status>Active</status><approver>Board</approver><last-revision><date>2020-02-18</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Voted to Active by Board on 2019-03-07. Sorry for the delay in the editor queue.</remark></last-revision><sig>None</sig><lastcall>2018-01-27</lastcall></xep><xep accepted="true"><number>346</number><title>Form Discovery and Publishing</title><abstract>This specification describes a series of conventions that allow the management of form templates and publishing of completed forms.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>347</number><title>Internet of Things - Discovery</title><abstract>This specification describes an architecture based on the XMPP protocol whereby Things can be installed and safely discovered by their owners and connected into networks of Things.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>iot-discovery</shortname><last-revision><date>2018-11-03</date><version>0.5.1</version><initials>pep</initials><remark>Fix a bunch of typos, batch-style.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>348</number><title>Signing Forms</title><abstract>This specification describes a method whereby a client can sign a form using credentials not related to the current connection.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>signing-forms</shortname><last-revision><date>2017-09-11</date><version>0.3</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>349</number><title>Rayo Clustering</title><abstract>This specification describes an extension to the Rayo protocol to support clustering of Rayo servers and their presentation as a unified service.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>350</number><title>Data Forms Geolocation Element</title><abstract>This specification defines an XMPP protocol extension for including geolocation data in XEP-0004 data forms.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>geolocation-element</shortname><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>351</number><title>Recipient Server Side Notifications Filtering</title><abstract>This specification defines a modern efficient way to deliver PubSub notifications.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>352</number><title>Client State Indication</title><abstract>This document defines a way for the client to indicate its active/inactive state.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>csi</shortname><last-revision><date>2020-10-14</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted as Draft as per Council vote from 2020-08-26.</remark></last-revision><sig>Standards</sig><lastcall>2020-08-18</lastcall></xep><xep accepted="true"><number>353</number><title>Jingle Message Initiation</title><abstract>This specification provides a way for the initiator of a Jingle session to propose sending an invitation in an XMPP message stanza, thus taking advantage of message delivery semantics instead of sending IQ stanzas to all of the responder's online resources or choosing a particular online resource.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>jingle-message</shortname><last-revision><date>2022-01-29</date><version>0.6.0</version><initials>tm</initials><remark>
      Port version 0.5 to :0 namespace and improve tie-breaking section
    </remark></last-revision><sig>Standards</sig><lastcall>2019-08-13</lastcall></xep><xep accepted="true"><number>354</number><title>Customizable Message Routing</title><abstract>This specification specifies customizable behavior of RFC 6121 section 8.5.2.1.1 to allow various message routing algorithms (e.g., for load balancing).</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>355</number><title>Namespace Delegation</title><abstract>This specification provides a way for XMPP server to delegate treatments for a namespace to an other entity</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2021-10-15</date><version>0.5</version><initials>jp</initials><remark>* delegation of 
* delegation of 
*  about disco requests
* namespace bump
* typos</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>356</number><title>Privileged Entity</title><abstract>This specification provides a way for XMPP entities to have a privileged access to some other entities data</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2023-04-24</date><version>0.4.1</version><initials>gh/@bodqhrohro</initials><remark>Fixed some typos</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>357</number><title>Push Notifications</title><abstract>This specification defines a way for an XMPP servers to deliver information for use in push notifications to mobile and other devices.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>push</shortname><last-revision><date>2020-02-11</date><version>0.4.1</version><initials>@sonnyp</initials><remark>Fix document-internal link</remark></last-revision><sig>Standards</sig><lastcall>2020-04-15</lastcall></xep><xep accepted="true"><number>358</number><title>Publishing Available Jingle Sessions</title><abstract>This specification defines an XMPP protocol extension that enables an XMPP entity to advertise the fact that it is willing accept a particular Jingle session request. The protocol is used mainly to inform other entities that a particular file is available for transfer via the Jingle File Transfer protocol defined in XEP-0234.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jinglepub</shortname><last-revision><date>2017-09-11</date><version>0.4</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>359</number><title>Unique and Stable Stanza IDs</title><abstract>This specification describes unique and stable IDs for messages.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>stanza-id</shortname><last-revision><date>2023-02-20</date><version>0.7.0</version><initials>fs</initials><remark>Add security consideration regarding spoofability and reference example</remark></last-revision><sig>Standards</sig><lastcall>2018-11-03</lastcall></xep><xep accepted="true"><number>360</number><title>Nonzas (are not Stanzas)</title><abstract>This specification defines the term "Nonza", describing every top level stream element that is not a Stanza.</abstract><type>Standards Track</type><status>Rejected</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig><lastcall>2024-03-25</lastcall></xep><xep accepted="true"><number>361</number><title>Zero Handshake Server to Server Protocol</title><abstract>This specification defines an approach for a pair of servers to eliminate initial handshakes and associated data transfer when using the XMPP S2S Protocol. This approach may only be used with a priori agreement and configuration of the two servers involved. This is of significant benefit in high latency environments.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><shortname>X2X</shortname><last-revision><date>2017-09-11</date><version>0.3</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>362</number><title>Raft over XMPP</title><abstract>This specification provides a means for transporting messages from the Raft consensus algorithm over XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>363</number><title>HTTP File Upload</title><abstract>This specification defines a protocol to request permissions from another entity to upload a file to a specific path on an HTTP server and at the same time receive a URL from which that file can later be downloaded again.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2022-01-04</date><version>1.1.0</version><initials>egp, mb</initials><remark>* Filename size in bytes.
* Headers MUST be included in the PUT request.
* Headers considered opaque.
* Servers may want to sign headers, in security implications.
* Allow header case insensitivity, multiple times the same header, and preserve the order in the HTTP request.</remark></last-revision><sig>Standards</sig><lastcall>2020-01-28</lastcall></xep><xep accepted="true"><number>364</number><title>Current Off-the-Record Messaging Usage</title><abstract>This document outlines the current usage of Off-the-Record messaging in XMPP, its drawbacks, its strengths, and recommendations for improving the end user experience.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><last-revision><date>2019-08-20</date><version>0.3.2</version><initials>jublah</initials><remark>Fix broken link to Daniels article</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>365</number><title>Server to Server communication over STANAG 5066 ARQ</title><abstract>This specification defines operation over XMPP over the NATO STANAG 5066 data link service for point to point links (ARQ). This enables optimized XMPP performance over HF Radio (which STANAG 5066 was designed for) and over other data links using STANAG 5066.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>S5066</shortname><last-revision><date>2022-03-28</date><version>0.3</version><initials>sek</initials><remark>Make use of SLEP Streaming service, which was not available for 0.1.  This provides a better service mapping than direct use of 5066 and provides compression.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>366</number><title>Entity Versioning</title><abstract>A method by which lists of items may be versioned so that servers will not need to send the entire list if it has not been modified, saving bandwidth and time with minimal state being stored by the server and client.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>EV</shortname><last-revision><date>2016-12-21</date><version>0.1.2</version><initials>ssw</initials><remark>Spelling, tone, and grammar.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>367</number><title>Message Attaching</title><abstract>This specification defines a method for indicating that a message contains content which describes an earlier message in the conversation and should be grouped with the earlier message.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>message-attaching</shortname><last-revision><date>2018-08-18</date><version>0.3</version><initials>mw</initials><remark>Update to use unique stanza ids.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>368</number><title>SRV records for XMPP over TLS</title><abstract>This specification defines a procedure to look up xmpps-client/xmpps-server SRV records (for direct TLS connections) in addition to xmpp-client/xmpp-server and mix weights/priorities.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><last-revision><date>2019-08-20</date><version>1.1.0</version><initials>jsc</initials><remark>Describe how to fall back if _xmpps-server/_xmpps-client records cannot be found.</remark></last-revision><sig>Standards</sig><lastcall>2017-02-22</lastcall></xep><xep accepted="true"><number>369</number><title>Mediated Information eXchange (MIX)</title><abstract>This document defines Mediated Information eXchange (MIX), an XMPP protocol extension for the exchange of information among multiple users through a mediating service. The protocol can be used to provide human group communication and communication between non-human entities using channels, although with greater flexibility and extensibility than existing groupchat technologies such as Multi-User Chat (MUC). MIX uses Publish-Subscribe to provide flexible access and publication, and uses Message Archive Management (MAM) to provide storage and archiving.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>MIX-CORE</shortname><last-revision><date>2020-12-01</date><version>0.14.6</version><initials>gh/@mathieui</initials><remark>Fix minor typo</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>370</number><title>Jingle HTTP Transport Method</title><abstract>This specification defines two Jingle transport methods for establishing HTTP connections for either uploading or downloading data.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>371</number><title>Jingle ICE Transport Method</title><abstract>This specification defines a Jingle transport method that results in sending media data using datagram associations via the User Datagram Protocol (UDP) or using end-to-end connections via the Transport Control Protocol (TCP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology (which provides robust NAT traversal for media traffic) and also supports the ability to exchange candidates throughout the life of the session, consistent with so-called "Trickle ICE" (draft-ietf-ice-trickle).</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jingle-ice</shortname><supersedes><spec>XEP-0176</spec></supersedes><last-revision><date>2021-03-04</date><version>0.3.1</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>372</number><title>References</title><abstract>This document defines a method for one XMPP stanza to provide references to another entity, such as mentioning users, HTTP resources, or other XMPP resources.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>Refs</shortname><last-revision><date>2020-12-09</date><version>0.5.0</version><initials>kis</initials><remark>Specify counting should be of code points.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>373</number><title>OpenPGP for XMPP</title><abstract>Specifies end-to-end encryption and authentication of data with the help of OpenPGP, announcement, discovery and retrieval of public keys and a mechanism to synchronize secret keys over multiple devices.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>ox</shortname><last-revision><date>2021-05-04</date><version>0.7.0</version><initials>ps</initials><remark>Recommend PubSub access model 'open' for public key data node and metadata node.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>374</number><title>OpenPGP for XMPP Instant Messaging</title><abstract>Specifies a OpenPGP for XMPP (XEP-0373) profile for the Instant Messaging (IM) use case.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>oxim</shortname><last-revision><date>2018-01-25</date><version>0.2.0</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>375</number><title>XMPP Compliance Suites 2016</title><abstract>This document defines XMPP protocol compliance levels for 2016.</abstract><type>Standards Track</type><status>Retracted</status><approver>Council</approver><shortname>CS2016</shortname><supersedes><spec>XEP-0302</spec></supersedes><supersededby><spec>XEP-0387</spec></supersededby><last-revision><date>2016-07-20</date><version>0.3</version><initials>ssw</initials><remark>Don't require both BOSH and Websockets.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>376</number><title>Pubsub Account Management</title><abstract>This specification describes a new model for handling remote pubsub services and a protocol for doing so.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>pam</shortname><last-revision><date>2017-09-11</date><version>0.2</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>377</number><title>Spam Reporting</title><abstract>This document specifies a mechanism by which users can report spam and other abuse to a server operator or other spam service.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2023-04-03</date><version>0.3.1</version><initials>egp</initials><remark>Add XML Schema.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>378</number><title>OTR Discovery</title><abstract>This document provides a mechanism by which OTR encryption support can be discovered in XMPP, without relying on OTRs protocol agnostic discovery mechanism.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>OTR-DISCO</shortname><last-revision><date>2017-09-11</date><version>0.1</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>379</number><title>Pre-Authenticated Roster Subscription</title><abstract>This document defines a protocol and URI scheme for pre-authenticated roster links that allow a third party to automatically obtain the user's presence subscription. The goal of this is to make onboarding of new XMPP IM contacts as easy as possible.</abstract><type>Standards Track</type><status>Proposed</status><approver>Council</approver><shortname>pars</shortname><last-revision><date>2021-03-04</date><version>0.3.3</version><initials>mw</initials><remark>Cross-document editorial adjustments for inclusive language.</remark></last-revision><sig>Standards</sig><lastcall>2021-10-20</lastcall></xep><xep accepted="true"><number>380</number><title>Explicit Message Encryption</title><abstract>This specification provides a way to mark encrypted messages so the recipient can discover how to decrypt it.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>EME</shortname><last-revision><date>2021-11-18</date><version>0.4.0</version><initials>melvo</initials><remark>Add new OMEMO namespaces:
* Add 'urn:xmpp:omemo:1' for OMEMO versions since 0.4.0
* Add 'urn:xmpp:omemo:2' for OMEMO versions since 0.8.0</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>381</number><title>Internet of Things Special Interest Group (IoT SIG)</title><abstract>This document proposes the formation of a Special Interest Group SIG) within the XSF devoted to the application of XMPP technologies to the Internet of Things (IoT).</abstract><type>Procedural</type><status>Active</status><approver>Council</approver><last-revision><date>2021-07-27</date><version>1.0.0</version><initials>XEP Editor: jsc</initials><remark>Accepted by Council</remark></last-revision><sig>None</sig><lastcall>2020-12-15</lastcall></xep><xep accepted="true"><number>382</number><title>Spoiler messages</title><abstract>This specification defines an XMPP protocol extension that provides a method for indicating a message is a spoiler and should be displayed as such.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>spoilers</shortname><last-revision><date>2018-01-25</date><version>0.2.0</version><initials>XEP Editor (jwi)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>383</number><title>Burner JIDs</title><abstract>A mechanism by which users may request anonymous, ephemeral "burner" JIDs.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>burner</shortname><last-revision><date>2021-07-10</date><version>0.2.0</version><initials>ssw</initials><remark>Improve security considerations and add listing JIDs.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>384</number><title>OMEMO Encryption</title><abstract>This specification defines a protocol for end-to-end encryption in one-to-one chats, as well as group chats where each participant may have multiple clients per account.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>OMEMO</shortname><last-revision><date>2022-01-18</date><version>0.8.3</version><initials>gh/@6k27f</initials><remark>Fix broken links</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>385</number><title>Stateless Inline Media Sharing (SIMS)</title><abstract>This specification describes a protocol for stateless asynchronous media sharing with integrity and transport flexibility. It allows clients to provide a good interoperable user experience in combination with Carbons and MAM.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>sims</shortname><last-revision><date>2018-01-25</date><version>0.2.1</version><initials>vv</initials><remark>Fix reference to XEP-0234.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>386</number><title>Bind 2</title><abstract>This specification provides a single-request replacement for several activities an XMPP client needs to do at startup.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>bind2</shortname><last-revision><date>2024-07-02</date><version>1.0.1</version><initials>egp</initials><remark>Add an XML Schema.</remark></last-revision><sig>Standards</sig><lastcall>2024-04-01</lastcall></xep><xep accepted="true"><number>387</number><title>XMPP Compliance Suites 2018</title><abstract>This document defines XMPP protocol compliance levels.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>CS2018</shortname><supersedes><spec>XEP-0375</spec></supersedes><supersededby><spec>XEP-0412</spec></supersededby><last-revision><date>2018-01-25</date><version>1.0.0</version><initials>XEP Editor (jwi)</initials><remark>Move to Draft as per Council vote on 2018-01-24.</remark></last-revision><sig>Standards</sig><lastcall>2017-12-21</lastcall></xep><xep accepted="true"><number>388</number><title>Extensible SASL Profile</title><abstract>This document describes a replacement for the SASL profile documented in RFC 6120 which allows for greater extensibility.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>sasl2</shortname><last-revision><date>2024-08-06</date><version>1.0.2</version><initials>egp</initials><remark>* Fix various invalid examples.
* Fix the XML Schema to match examples.</remark></last-revision><sig>Standards</sig><lastcall>2024-04-01</lastcall></xep><xep accepted="true"><number>389</number><title>Extensible In-Band Registration</title><abstract>This specification defines an XMPP protocol extension for in-band registration with instant messaging servers and other services with which an XMPP entity may initiate a stream. It aims to improve upon the state of the art and replace XEP-0077: In-Band Registration by allowing multi-factor registration mechanisms, and account recovery.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>ibr2</shortname><supersedes><spec>XEP-0077</spec></supersedes><last-revision><date>2020-11-17</date><version>0.6.0</version><initials>ssw</initials><remark>Error out if a client selects an invalid flow</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>390</number><title>Entity Capabilities 2.0</title><abstract>This document overhauls the XMPP protocol extension Entity Capabilities (XEP-0115). It defines an XMPP protocol extension for broadcasting and dynamically discovering client, device, or generic entity capabilities. In order to minimize network impact, the transport mechanism is standard XMPP presence broadcast (thus forestalling the need for polling related to service discovery data), the capabilities information can be cached either within a session or across sessions, and the format has been kept as small as possible.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>ecaps2</shortname><supersedes><spec>XEP-0115</spec></supersedes><last-revision><date>2018-03-05</date><version>0.3.2</version><initials>fs</initials><remark>Explain that ASCII Seperators are only invalid in XML 1.0, but not in XML 1.1.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>391</number><title>Jingle Encrypted Transports</title><abstract>This specification defines a method that allows to use established encryption schemes for end-to-end encryption of Jingle transports.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jet</shortname><last-revision><date>2018-07-31</date><version>0.1.2</version><initials>vv</initials><remark>Replace TI with IV</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>392</number><title>Consistent Color Generation</title><abstract>This specification provides a set of algorithms to consistently generate colors given a string. The string can be a nickname, a JID or any other piece of information. All entities adhering to this specification generate the same color for the same string, which provides a consistent user experience across platforms.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>colors</shortname><last-revision><date>2024-03-27</date><version>1.0.0</version><initials>XEP Editor (dg)</initials><remark>Accept as Stable as per Council Vote from 2024-03-27.</remark></last-revision><sig>Standards</sig><lastcall>2024-03-25</lastcall></xep><xep accepted="true"><number>393</number><title>Message Styling</title><abstract>This specification defines a formatted text syntax for use in instant messages with simple text styling.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>styling</shortname><supersedes><spec>XEP-0071</spec></supersedes><last-revision><date>2021-04-04</date><version>1.1.1</version><initials>ssw</initials><remark>
        General readability changes:
        Copy part of span definition from glossary to business rules and remove
        parenthesis for marking spans and blocks which was used inconsistently.
        Also merge two lists of examples.
      </remark></last-revision><sig>Standards</sig><lastcall>2020-05-26</lastcall></xep><xep accepted="true"><number>394</number><title>Message Markup</title><abstract>This specification provides an alternative to XHTML-IM with rigid separation of content and markup information, improving the resilience against spoofing and injection attacks.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>markup</shortname><last-revision><date>2024-07-13</date><version>0.3.0</version><initials>lmw</initials><remark>Add support for strong emphasis, declaring langauge on code blocks and making lists ordered.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>395</number><title>Atomically Compare-And-Publish PubSub Items</title><abstract>This specification provides a mechanism to atomically Compare-And-Publish items to a PubSub node.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>cap</shortname><last-revision><date>2018-12-06</date><version>0.2.0</version><initials>XEP Editor (jsc)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>396</number><title>Jingle Encrypted Transports - OMEMO</title><abstract>Extension for JET introducing OMEMO End-to-End Encrypted Jingle Transports.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>jet-omemo</shortname><last-revision><date>2018-12-06</date><version>0.2.0</version><initials>XEP Editor (jsc)</initials><remark>Defer due to lack of activity.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>397</number><title>Instant Stream Resumption</title><abstract>This specification introduces a mechanism for instant stream resumption, based on Stream Management (XEP-0198), allowing XMPP entities to instantaneously resume an XMPP stream.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>isr</shortname><last-revision><date>2018-11-03</date><version>0.1.1</version><initials>fs</initials><remark>Minor fixes and clarifications</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>398</number><title>User Avatar to vCard-Based Avatars Conversion</title><abstract>This specification describes a method for using PEP based avatars and vCard based avatars in parallel by having the user&#8217;s server do a conversion between the two.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>pep-vcard-conversion</shortname><last-revision><date>2024-05-06</date><version>1.0.0</version><initials>XEP Editor (dg)</initials><remark>Accept as Stable as per Council Vote from 2024-04-30.</remark></last-revision><sig>Standards</sig><lastcall>2024-04-14</lastcall></xep><xep accepted="true"><number>399</number><title>Client Key Support</title><abstract>This specification defines an XMPP binding of the supporting functions for the CLIENT-KEY SASL mechanism.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>client-key</shortname><last-revision><date>2018-01-25</date><version>0.1.0</version><initials>XEP Editor (jwi)</initials><remark>Accepted by vote of Council on 2018-01-10.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>400</number><title>Multi-Factor Authentication with TOTP</title><abstract>This specification defines support for multi-factor authentication in terms of SASL2 Tasks based around the Time-based One Time Password mechanism.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>mfa</shortname><last-revision><date>2018-01-25</date><version>0.1.0</version><initials>XEP Editor (jwi)</initials><remark>Accepted by vote of Council on 2018-01-10.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>401</number><title>Ad-hoc Account Invitation Generation</title><abstract>This document defines a protocol and URI scheme for user invitation in order to allow a third party to register on a server. The goal of this is to make onboarding for XMPP IM newcomers as easy as possible.</abstract><type>Standards Track</type><status>Proposed</status><approver>Council</approver><last-revision><date>2021-10-06</date><version>0.5.0</version><initials>gl</initials><remark>Factor out XEP-0445</remark></last-revision><sig>Standards</sig><lastcall>2021-10-20</lastcall></xep><xep accepted="true"><number>402</number><title>PEP Native Bookmarks</title><abstract>This specification defines a syntax and storage profile for keeping a list of chatroom bookmarks on the server.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>bookmarks2</shortname><supersedes><spec>XEP-0411</spec></supersedes><last-revision><date>2024-08-15</date><version>1.2.0</version><initials>mye</initials><remark>Encourage clients to immediately leave the room if they receive a bookmark notification with autojoin set to false</remark></last-revision><sig>Standards</sig><lastcall>2020-03-03</lastcall></xep><xep accepted="true"><number>403</number><title>Mediated Information eXchange (MIX): Presence Support.</title><abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369 to provide presence information for MIX clients to MIX channel participants. It also specifies relay of IQ stanzas through a MIX channel.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>MIX-PRESENCE</shortname><last-revision><date>2020-12-01</date><version>0.3.2</version><initials>gh/@mathieui</initials><remark>Fix incorrect namespaces</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>404</number><title>Mediated Information eXchange (MIX): JID Hidden Channels.</title><abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369. This specification extends MIX to provide a number of privacy control options and in particular JID Hidden Channels.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>MIX-ANON</shortname><last-revision><date>2020-12-01</date><version>0.3.1</version><initials>gh/@mathieui</initials><remark>Various XML example cleanup and fixes</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>405</number><title>Mediated Information eXchange (MIX): Participant Server Requirements</title><abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369. It specifies behaviour of an XMPP server to which MIX Clients connect in order to enable correct operation of these clients in conjunction with a MIX server.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>MIX-PAM</shortname><last-revision><date>2022-07-15</date><version>0.5.3</version><initials>lnj</initials><remark>Clarify that later roster requests reset the state of the annotation setting</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>406</number><title>Mediated Information eXchange (MIX): MIX Administration</title><abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369. This specification defines a framework for MIX administration and administration operations.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>MIX-ADMIN</shortname><last-revision><date>2022-03-22</date><version>0.3.1</version><initials>gl</initials><remark>Fix reference to PubSub namespace</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>407</number><title>Mediated Information eXchange (MIX): Miscellaneous Capabilities</title><abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369. It specifies a number of independent optional capabilities that MAY be used with MIX.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>MIX-MISC</shortname><last-revision><date>2020-11-03</date><version>0.1.2</version><initials>gh/@melvo</initials><remark>Fix various typos</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>408</number><title>Mediated Information eXchange (MIX): Co-existence with MUC</title><abstract>This document defines an extension to Mediated Information eXchange (MIX) specified in XEP-0369. It specifies how MIX and MUC can be operated together.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>MIX-MUC</shortname><last-revision><date>2021-03-09</date><version>0.2.0</version><initials>@mathieui</initials><remark>Fix reference to MIX-CORE namespaces</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>409</number><title>IM Routing-NG</title><abstract>This specification provides a new set of routing rules for modern instant messaging.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>IM-NG</shortname><last-revision><date>2018-06-05</date><version>0.1.0</version><initials>XEP Editor (jwi)</initials><remark>Accepted by vote of Council on 2018-04-11.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>410</number><title>MUC Self-Ping (Schr&#246;dinger's Chat)</title><abstract>This protocol extension for XEP-0045 Multi User Chat allows clients to check whether they are still joined to a chatroom.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>muc-selfping</shortname><last-revision><date>2019-09-25</date><version>1.1.0</version><initials>jsc</initials><remark>Treat remote-server-not-found and remote-server-timeout like timeout errors (i.e. undecided).</remark></last-revision><sig>Standards</sig><lastcall>2019-01-22</lastcall></xep><xep accepted="true"><number>411</number><title>Bookmarks Conversion</title><abstract>This specification describes a method to migrate to PEP based bookmarks without loosing compatibility with client that still use Private XML.</abstract><type>Standards Track</type><status>Deprecated</status><approver>Council</approver><shortname>bookmarks-conversion</shortname><supersededby><spec>XEP-0402</spec></supersededby><last-revision><date>2021-10-19</date><version>1.1.0</version><initials>XEP Editor (jsc)</initials><remark>Deprecated by vote of Council on 2021-10-06.</remark></last-revision><sig>Standards</sig><lastcall>2020-10-14</lastcall></xep><xep accepted="true"><number>412</number><title>XMPP Compliance Suites 2019</title><abstract>This document defines XMPP protocol compliance levels.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>CS2019</shortname><supersedes><spec>XEP-0387</spec></supersedes><supersededby><spec>XEP-0423</spec></supersededby><last-revision><date>2020-01-28</date><version>1.0.1</version><initials>XEP Editor (jsc)</initials><remark>Deprecate and Obsolete per Council vote on 2020-01-22</remark></last-revision><sig>Standards</sig><lastcall>2019-02-29</lastcall></xep><xep accepted="true"><number>413</number><title>Order-By</title><abstract>This specification allows to change order of items retrieval in a Pubsub or MAM query</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2021-07-21</date><version>0.2</version><initials>jp</initials><remark>Add a way to discover on which protocols Order-By applies
Remove references to SQL (except in implementation notes)
Specify that order-by operate on the whole item set and inside a RSM result set
Explicitly says that creation and modification dates are set by Pubsub service itself
Specify that Clark notation should be used for extensions
Add a full example with Pubsub and RSM
Add hint for SQL based implementations
removed XEP-0060 and XEP-0313 as dependencies, they are mentioned as use cases, but are not mandatory
better wording following feedback
Namespace bump</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>414</number><title>Cryptographic Hash Function Recommendations for XMPP</title><abstract>This document provides recommendations for the use of cryptographic hash functions in XMPP protocol extensions.</abstract><type>Informational</type><status>Deferred</status><approver>Council</approver><shortname>hashrecs</shortname><last-revision><date>2020-05-23</date><version>0.4.0</version><initials>rion</initials><remark>Make Blake2b-256 SHOULD and Blake2b 512 MUST</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>415</number><title>XMPP Over RELOAD (XOR)</title><abstract>This specification defines an XMPP Usage of REsource LOcation And Discovery (RELOAD). The XMPP usage provides an ability for XMPP clients to discover other peers' location through the peer-to-peer overlay. Once a peer location is determined, the RELOAD AppAttach method is used to establish a direct connection between peers through which XMPP streams are exchanged.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2019-03-06</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2019-02-27.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>416</number><title>E2E Authentication in XMPP</title><abstract>This specification describes how X.509 certificates can be used for end-to-end authentication in XMPP.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2019-03-06</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2019-02-27.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>417</number><title>E2E Authentication in XMPP: Certificate Issuance and Revocation</title><abstract>This specification defines a way for a certificate authority to serve certificate signing requests via XMPP in order to issue X.509 certificates for the use in end-to-end and c2s SASL EXTERNAL authentication.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2019-03-29</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2019-03-13.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>418</number><title>DNS Queries over XMPP (DoX)</title><abstract>This specification defines an XMPP protocol extension for sending DNS queries and getting DNS responses over XML streams. Each DNS query-response pair is mapped into an IQ exchange.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>dox</shortname><last-revision><date>2019-03-29</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2019-03-13.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>419</number><title>Improving Baseline Security in XMPP</title><abstract>This document describes a number of concrete and effective mechanisms for offering significant security enhancements to XMPP, with broad applicability.</abstract><type>Humorous</type><status>Active</status><approver>Editor</approver><shortname>security-theatre</shortname><last-revision><date>2019-04-01</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Acceptance as XEP-0419; Light editing.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>420</number><title>Stanza Content Encryption</title><abstract>The Stanza Content Encryption (SCE) protocol is intended as a way to allow clients to securely exchange arbitrary extension elements using different end-to-end encryption schemes.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>SCE</shortname><last-revision><date>2021-11-18</date><version>0.4.1</version><initials>melvo</initials><remark>Clarify bare JID usage and improve sentences:
* Clarify usage of bare JIDs for affix elements
* Improve and correct sentences about affix elements</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>421</number><title>Occupant identifiers for semi-anonymous MUCs</title><abstract>This specification defines a method that allows clients to identify a MUC participant across reconnects and renames. It thus prevents impersonification of semi-anonymous users.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>occupant-id</shortname><last-revision><date>2025-01-15</date><version>1.0.0</version><initials>XEP Editor (dg)</initials><remark>Accept as Stable as per Council Vote from 2025-01-14.</remark></last-revision><sig>Standards</sig><lastcall>2025-01-06</lastcall></xep><xep accepted="true"><number>422</number><title>Message Fastening</title><abstract>This specification defines a way for payloads on a message to be marked as being logically fastened to a previous message.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>fasten</shortname><last-revision><date>2019-12-30</date><version>0.2.0</version><initials>ks/dwd</initials><remark>Preparation for extending MAM</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>423</number><title>XMPP Compliance Suites 2020</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>CS2020</shortname><supersedes><spec>XEP-0412</spec></supersedes><supersededby><spec>XEP-0443</spec></supersededby><last-revision><date>2022-02-15</date><version>1.0.1</version><initials>gl</initials><remark>Add supersededby</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>424</number><title>Message Retraction</title><abstract>This specification defines a method for indicating that a message should be retracted.</abstract><type>Standards Track</type><status>Proposed</status><approver>Council</approver><shortname>message-retract</shortname><last-revision><date>2025-01-18</date><version>0.4.2</version><initials>jcb</initials><remark>* Use a XEP-0425 /me command in the fallback body
* State that a tombstone's &lt;retracted/&gt; element's 'id' attribute should match the retraction message's 'id'.
* Specify XEP-0359 as a dependency and require that the stanza 'id' be used instead of the origin-id.
* Update the "Security Considerations" to mention the risk of non-unique message IDs.</remark></last-revision><sig>Standards</sig><lastcall>2025-01-06</lastcall></xep><xep accepted="true"><number>425</number><title>Moderated Message Retraction</title><abstract>This specification defines a method for groupchat moderators to retract messages of other users.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>message-moderation</shortname><last-revision><date>2023-03-02</date><version>0.3.0</version><initials>jcb</initials><remark>* Remove the dependency on XEP-0422 Message Fastening
* Rename to 'Moderated Message Retraction' and focus only on the retraction use-case
* Ensure compatibility with clients that only implement XEP-0424
* Clarify the purpose of the &lt;reason/&gt; element</remark></last-revision><sig>Standards</sig><lastcall>2022-01-04</lastcall></xep><xep accepted="true"><number>426</number><title>Character counting in message bodies</title><abstract>This document describes how to correctly count characters in message bodies. This is required when referencing a position in the body.</abstract><type>Informational</type><status>Experimental</status><approver>Council</approver><shortname>charcount</shortname><last-revision><date>2022-12-27</date><version>0.3.0</version><initials>lmw</initials><remark>Added section about subsequences.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>427</number><title>MAM Fastening Collation</title><abstract>This specification proposes a mechanism by which MAM results containing fastenings can be collated effectively.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>mamfc</shortname><last-revision><date>2020-01-28</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-01-02.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>428</number><title>Fallback Indication</title><abstract>This specification proposes a mechanism by which message bodies or parts thereof can be marked as being for fallback purposes, and therefore to be ignored by anything that understands the original intent of the message.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>fallback</shortname><last-revision><date>2024-03-20</date><version>0.2.1</version><initials>lnj</initials><remark>Change integer type of region start and end attributes in schema to xs:unsignedInt.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>429</number><title>Special Interests Group End to End Encryption</title><abstract>This document proposes the formation of a Special Interest Group (SIG) within the XSF devoted to the development of end-to-end encryption within the context of XMPP.</abstract><type>Procedural</type><status>Active</status><approver>Council</approver><shortname>SIG-E2EE</shortname><last-revision><date>2021-08-10</date><version>1.1.0</version><initials>mw</initials><remark>Add discussion venue after creation by the Infrastructure Team.</remark></last-revision><sig>None</sig><lastcall>2020-12-15</lastcall></xep><xep accepted="true"><number>430</number><title>Inbox</title><abstract>This specification proposes a mechanism by which clients can find a list of ongoing conversations and their state.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>inbox</shortname><last-revision><date>2020-02-03</date><version>0.2.0</version></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>431</number><title>Full Text Search in MAM</title><abstract>This specification proposes a field in the MAM form for full text searching.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>fulltextmam</shortname><last-revision><date>2020-01-29</date><version>0.2.0</version><initials>dwd</initials><remark>* No More Beer
* Quasi-normative language around syntactic implementation</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>432</number><title>Simple JSON Messaging</title><abstract>This specification proposes a simple mechanism by which applications can transfer data safely, without needing additional protocol design work. It is intended to provide a protocol that is trivial to implement and can be driven with a simple API.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>udt</shortname><last-revision><date>2022-04-12</date><version>0.1.1</version><initials>fs</initials><remark>Declare missing dependency on XEP-0335.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>433</number><title>Extended Channel Search</title><abstract>This specification provides a standardised protocol to search for public group chats. In contrast to XEP-0030 (Service Discovery), it works across multiple domains and in contrast to XEP-0055 (Jabber Search) it more clearly handles extensibility.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>ECS</shortname><last-revision><date>2020-02-27</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-02-26.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>434</number><title>Trust Messages (TM)</title><abstract>This document specifies a way to communicate the trust in public long-term keys used by end-to-end encryption protocols from one endpoint to another.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>TM</shortname><last-revision><date>2021-10-04</date><version>0.6.0</version><initials>melvo</initials><remark>Specify key identifier encoding, improve glossary and update to XEP-0384 version 0.8.0:
* Specify usage of Base64 encoding for key identifiers within trust messages
* Specify usage of Base16 encoding for key identifiers within Trust Message URIs
* Use Base64-encoded key identifiers in examples
* Add 'hash value' as example of key identifier
* Update OMEMO's namespace to 'urn:xmpp:omemo:2'
* Update namespace to 'urn:xmpp:tm:1'</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>435</number><title>Reminders</title><abstract>This specification provides a way to set up reminders.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2020-03-31</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-03-04.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>436</number><title>MUC presence versioning</title><abstract>This specification defines a versioning mechanism which reduces the amount of presence traffic in a XEP-0045 MUC</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><shortname>omnipresent-muc-affiliates</shortname><last-revision><date>2020-05-10</date><version>0.2.0</version><initials>jcb</initials><remark>Incorporate feedback from the standards list
* Create a separate tag for sending the version number.
* Include a reset token.
* Remove the "Additional measures" section and merge parts into "Requirements".
* Mandate that presences are always sent for affiliated users.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>437</number><title>Room Activity Indicators</title><abstract>This specification describes a lightweight mechanism for activity notifications in MUCs</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2020-05-05</date><version>0.2.0</version><initials>XEP Editor (jsc)</initials><remark>Assign urn:xmpp namespace instead of xmpp:prosody.im namespace (this was missed during acceptance)</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>438</number><title>Best practices for password hashing and storage</title><abstract>This document outlines best practices for handling user passwords on the public Jabber network for both clients and servers.</abstract><type>Informational</type><status>Experimental</status><approver>Council</approver><shortname>passwords</shortname><last-revision><date>2020-10-30</date><version>0.2.0</version><initials>ssw</initials><remark>Update to match draft-ietf-kitten-password-storage-01.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>439</number><title>Quick Response</title><abstract>Quickly respond to automated messages.</abstract><type>Standards Track</type><status>Deferred</status><approver>Council</approver><last-revision><date>2020-05-05</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-04-22.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>440</number><title>SASL Channel-Binding Type Capability</title><abstract>This specification allows servers to annouce their supported SASL channel-binding types to clients.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>sasl-cb-types</shortname><last-revision><date>2024-07-02</date><version>0.4.2</version><initials>egp</initials><remark>* Add an XML schema.
* Mention that this specification does add a new namespace that should go to the registrar.
* Fix indentation, typos, misuse of '' vs. &lt;/&gt; for elements, etc.</remark></last-revision><sig>Standards</sig><lastcall>2024-05-20</lastcall></xep><xep accepted="true"><number>441</number><title>Message Archive Management Preferences</title><abstract>This document defines a protocol to control a user's archiving preferences.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>mamprefs</shortname><last-revision><date>2020-08-25</date><version>0.2.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-08-19.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>442</number><title>Pubsub Message Archive Management</title><abstract>This document defines a protocol to query and control a pubsub node's message archive.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-mam</shortname><last-revision><date>2020-08-25</date><version>0.2.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-08-19.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>443</number><title>XMPP Compliance Suites 2021</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>CS2021</shortname><supersedes><spec>XEP-0423</spec></supersedes><supersededby><spec>XEP-0459</spec></supersededby><last-revision><date>2020-11-24</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Accept as Draft as per Council vote from 2020-11-11.</remark></last-revision><sig>Standards</sig><lastcall>2020-11-03</lastcall></xep><xep accepted="true"><number>444</number><title>Message Reactions</title><abstract>This specification defines a way for adding reactions to a message.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>reactions</shortname><last-revision><date>2024-04-15</date><version>0.2.1</version><initials>wb</initials><remark>fix grammar and spelling</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>445</number><title>Pre-Authenticated In-Band Registration</title><abstract>This document extends the In-Band-Registration protocol to use invitation tokens, e.g. for registering accounts on non-public servers.</abstract><type>Standards Track</type><status>Proposed</status><approver>Council</approver><shortname>ibr-token</shortname><last-revision><date>2020-11-24</date><version>0.2.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-11-04.</remark></last-revision><sig>Standards</sig><lastcall>2021-10-20</lastcall></xep><xep accepted="true"><number>446</number><title>File metadata element</title><abstract>This specification defines a generic file metadata element to be used in other specifications.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>file-metadata</shortname><last-revision><date>2022-07-17</date><version>0.2.0</version><initials>lmw</initials><remark>Use height/width instead of dimensions</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>447</number><title>Stateless file sharing</title><abstract>This specification describes a protocol for stateless asynchronous file sharing with integrity and transport flexibility. It allows clients to provide a good interoperable user experience in combination with Carbons and MAM.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>sfs</shortname><last-revision><date>2024-01-01</date><version>0.3.1</version><initials>lmw</initials><remark>Fix example for multiple files.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>448</number><title>Encryption for stateless file sharing</title><abstract>This specification provides a protocol for sharing encrypted files using the stateless file sharing protocol (XEP-0447).</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>esfs</shortname><last-revision><date>2022-07-17</date><version>0.2.0</version><initials>lmw</initials><remark>* Replace the ProtoXEP reference with a reference to the published XEP.
* Add urn:xmpp:ciphers:aes-256-cbc-pkcs7:0 (same as used in XEP-0384).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>449</number><title>Stickers</title><abstract>This specification provides a protocol to send stickers and to create and share sticker packs.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>stickers</shortname><last-revision><date>2022-02-10</date><version>0.1.1</version><initials>egp</initials><remark>* Replace ProtoXEP references with actual XEP references.
* Use XEP-0446&#8217;s  instead of the typo&#8217;d .</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>450</number><title>Automatic Trust Management (ATM)</title><abstract>This document specifies a way to automatically manage the trust in public long-term keys used by end-to-end encryption protocols.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>ATM</shortname><last-revision><date>2021-10-04</date><version>0.4.0</version><initials>melvo</initials><remark>Update to XEP-0434 version 0.6.0 and XEP-0384 version 0.8.0:
* Use Base64-encoded key identifiers in examples
* Update TM's namespace to 'urn:xmpp:tm:1'
* Update OMEMO's namespace to 'urn:xmpp:omemo:2'</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>451</number><title>Stanza Multiplexing</title><abstract>This spec provides a mechanism for multiplexing multiple virtual hosts over a single XMPP session.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>mux</shortname><supersedes><spec>XEP-0220</spec></supersedes><last-revision><date>2021-01-19</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2020-12-09.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>452</number><title>MUC Mention Notifications</title><abstract>This specification documents how a user may be informed when they're mentioned in a MUC which they're not currently joined to.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2022-01-11</date><version>0.2.2</version><initials>gh/@xnamed</initials><remark>Fix addresses in example</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>453</number><title>DOAP usage in XMPP</title><abstract>This specification defines how XMPP projects can provide a machine-readable description of their abilities, and how external entities can interact with it.</abstract><type>Informational</type><status>Experimental</status><approver>Council</approver><last-revision><date>2023-07-04</date><version>0.1.2</version><initials>spw</initials><remark>Fix XMLNS typo</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>454</number><title>OMEMO Media sharing</title><abstract>An informal way of sharing media files despite limitations in the OMEMO encryption</abstract><type>Historical</type><status>Experimental</status><approver>Council</approver><last-revision><date>2021-01-26</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2021-01-13.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>455</number><title>Service Outage Status</title><abstract>This document defines an XMPP protocol extension that enables server administrators to communicate issues with the server to all users in a semantic manner.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2021-02-09</date><version>0.2.0</version><remark>Evolve the standard: Editorial restructuring, add business rules and security considerations and clarify some wording.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>456</number><title>Content Rating Labels</title><abstract>This specification provides a wire format in the form of a Service Discovery extension to allow services of various kinds to publish information about the kind of content they allow and/or endorse on their platform.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>crl</shortname><last-revision><date>2021-03-28</date><version>0.2.0</version><initials>jsc</initials><remark>Describe the conversion algorithm.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>457</number><title>Message Fancying</title><abstract>This specification defines a Unicode-formatted fancy text syntax for use in instant messages.</abstract><type>Humorous</type><status>Active</status><approver>Editor</approver><shortname>fancying</shortname><supersedes><spec>XEP-0071</spec><spec>XEP-0393</spec><spec>XEP-0394</spec></supersedes><last-revision><date>2021-04-01</date><version>1.0.0</version><initials>XEP Editor (jsc)</initials><remark>Initial published version.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>458</number><title>Community Code of Conduct</title><abstract>This document describes the XMPP Standard Foundation's Code of Conduct.</abstract><type>Procedural</type><status>Active</status><approver>Board</approver><last-revision><date>2024-01-15</date><version>1.0.0</version><initials>psa</initials><remark>Changed status to Active per Board vote on 2024-01-05.</remark></last-revision><sig>None</sig></xep><xep accepted="true"><number>459</number><title>XMPP Compliance Suites 2022</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>Obsolete</status><approver>Council</approver><shortname>CS2022</shortname><supersedes><spec>XEP-0443</spec></supersedes><supersededby><spec>XEP-0479</spec></supersededby><last-revision><date>2021-12-01</date><version>1.1.0</version><initials>egp</initials><remark>Replace deprecated XEP-0411 with XEP-0402 in Advanced Group Chat.</remark></last-revision><sig>Standards</sig><lastcall>2021-09-21</lastcall></xep><xep accepted="true"><number>460</number><title>Pubsub Caching Hints</title><abstract>This specification provides a way to get caching information from a Pubsub node</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-caching</shortname><last-revision><date>2021-08-10</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2021-07-21.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>461</number><title>Message Replies</title><abstract>This document defines a way to indicate that a message is a reply to a previous message.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>reply</shortname><last-revision><date>2022-12-09</date><version>0.2.0</version><initials>nc</initials><remark>Fix example character counting. Add disco feature. Relax the 'to' attribute constraints.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>462</number><title>PubSub Type Filtering</title><abstract>This specification provides a way to filter PubSub nodes in a disco query.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2022-04-22</date><version>0.1.1</version><initials>pep</initials><remark>Wording, typos.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>463</number><title>MUC Affiliations Versioning</title><abstract>This specification provides a way to reduce the amount of queries necessary to stay up-to-date with affiliations in a MUC room.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2022-03-08</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-02-16.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>464</number><title>Cookies</title><abstract>This document defines an XMPP protocol extension for setting and sending cookies.</abstract><type>Humorous</type><status>Active</status><approver>Council</approver><shortname>cookies</shortname><last-revision><date>2022-04-01</date><version>1.0</version><initials>tjb</initials><remark>Publish initial version via fast track (XEP Editor: jsc).</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>465</number><title>Pubsub Public Subscriptions</title><abstract>This specification provides a way to make subscriptions to a node public</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pps</shortname><last-revision><date>2022-07-25</date><version>0.1.1</version><initials>J&#233;r&#244;me Poisson (jp)</initials><remark>Update Security Considerations according to council feedback.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>466</number><title>Ephemeral Messages</title><abstract>This specification encourages a shift in privacy settings wrt. logging policies.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2022-05-17</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-05-03.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>467</number><title>XMPP over QUIC</title><abstract>This specification defines a procedure to make both c2s and s2s XMPP connections over the QUIC protocol instead of TCP+TLS.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2022-07-13</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-06-22.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>468</number><title>WebSocket S2S</title><abstract>This specification defines a procedure to make s2s XMPP connections over WebSocket.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2022-07-13</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-06-22.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>469</number><title>Bookmark Pinning</title><abstract>This document defines an XMPP protocol extension to allow users to pin PEP Native Bookmarks.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>bookmarkspinning</shortname><last-revision><date>2022-08-23</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-07-27.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>470</number><title>Pubsub Attachments</title><abstract>This specification provides a way to attach elements to a pubsub item.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-attachments</shortname><last-revision><date>2022-08-25</date><version>0.2.0</version><initials>jp</initials><remark>* 
              Update reactions to be similar to 
          
* 
              Namespace bump
          </remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>471</number><title>Events</title><abstract>This specification describe how to handle events with XMPP.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>events</shortname><last-revision><date>2022-12-13</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-09-28.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>472</number><title>Pubsub Social Feed</title><abstract>This specification defines a way of publishing social content over XMPP.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>psf</shortname><supersedes><spec>XEP-0277</spec></supersedes><last-revision><date>2023-04-03</date><version>0.2.0</version><initials>tj</initials><remark>* Change the pubsub#type to be consistent with other XEPs
* Add a Discovery section</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>473</number><title>OpenPGP for XMPP Pubsub</title><abstract>Specifies an OpenPGP for XMPP (XEP-0373) profile for the pubsub use case.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>oxps</shortname><last-revision><date>2022-12-13</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-10-19.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>474</number><title>SASL SCRAM Downgrade Protection</title><abstract>This specification provides a way to secure the SASL and SASL2 handshakes against method and channel-binding downgrades.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>SSDP</shortname><last-revision><date>2025-01-24</date><version>0.4.0</version><initials>tm</initials><remark>* Use better value delimiter</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>475</number><title>Pubsub Signing</title><abstract>Specifies a mechanism to sign pubsub items</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-signing</shortname><last-revision><date>2022-12-20</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-11-30.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>476</number><title>Pubsub Signing: OpenPGP Profile</title><abstract>Specifies a pubsub signing profile for OpenPGP</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pss-ox</shortname><last-revision><date>2022-12-20</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-11-30.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>477</number><title>Pubsub Targeted Encryption</title><abstract>Specifies a way to encrypt pubsub items for a restricted set of entities</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pte</shortname><last-revision><date>2022-12-20</date><version>0.1.0</version><initials>XEP Editor (jsc)</initials><remark>Accepted by vote of Council on 2022-11-30.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>478</number><title>Stream Limits Advertisement</title><abstract>This specification defines a way for an XMPP entity to announce the limits it will enforce for data received on a stream.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>sla</shortname><last-revision><date>2024-08-02</date><version>0.2.0</version><initials>egp</initials><remark>* Add the XML Schema.
* Clarify that both children can be optional.
* Fix indentation and one typo.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>479</number><title>XMPP Compliance Suites 2023</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>CS2023</shortname><supersedes><spec>XEP-0459</spec></supersedes><last-revision><date>2023-05-04</date><version>0.1.0</version><initials>XEP Editor: ks</initials><remark>Promote to Experimental.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>480</number><title>SASL Upgrade Tasks</title><abstract>This specification provides a way to upgrade to newer SASL mechanisms using SASL2 tasks.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>sut</shortname><last-revision><date>2024-12-01</date><version>0.2.0</version><initials>tm</initials><remark>Fix SCRAM upgrade description and XML schema.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>481</number><title>Content Types in Messages</title><abstract>This specification describes a generic method whereby content in messages can be tagged as having a specific Internet Content Type. It also provides a method for sending the same content using different content types, as a fall-back mechanism when communicating between clients having different content type support.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>content</shortname><last-revision><date>2023-05-04</date><version>0.1.0</version><initials>XEP Editor: ks</initials><remark>Promoting to Experimental.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>482</number><title>Call Invites</title><abstract>This document defines how to invite someone to a call and how to respond to the invite.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>call-invites</shortname><last-revision><date>2023-05-04</date><version>0.1.0</version><initials>XEP Editor: ks</initials><remark>Promoting to Experimental.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>483</number><title>HTTP Online Meetings</title><abstract>This specification defines a protocol extension to request URLs from an external HTTP entity usable to initiate and invite participants to an online meeting.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>http_online-meetings</shortname><last-revision><date>2023-12-12</date><version>0.2.0</version><initials>do</initials><remark>* Use XEP-0482 to send the meeting link to another party</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>484</number><title>Fast Authentication Streamlining Tokens</title><abstract>This specification defines a token-based method to streamline authentication in XMPP, allowing fully authenticated stream establishment within a single round-trip.</abstract><type>Standards Track</type><status>Proposed</status><approver>Council</approver><shortname>fast</shortname><last-revision><date>2024-06-30</date><version>0.2.0</version><initials>egp</initials><remark>* Added an XML Schema.
* Fixed text where 'count' was assumed to be an element, not an attribute.
* Fixed indentation in a few examples.</remark></last-revision><sig>Standards</sig><lastcall>2025-01-27</lastcall></xep><xep accepted="true"><number>485</number><title>PubSub Server Information</title><abstract>This document defines a data format whereby basic information of an XMPP domain can be expressed and exposed over pub-sub.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>serverinfo</shortname><last-revision><date>2024-03-10</date><version>0.1.0</version><initials>dg</initials><remark>* Promoted to Experimental.</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>486</number><title>MUC Avatars</title><abstract>This specification describes how to publish and retrieve avatars in rooms.</abstract><type>Historical</type><status>Experimental</status><approver>Council</approver><last-revision><date>2024-03-10</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>487</number><title>Host Meta 2 - One Method To Rule Them All</title><abstract>This document defines an XMPP Extension Protocol for extending XEP-0156 by modifying the JSON Web Host Metadata Link format to support discovering all possible XMPP connection methods, for c2s and s2s</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>connections-v2</shortname><supersedes><spec>XEP-0156</spec><spec>RFC 7711</spec></supersedes><last-revision><date>2024-03-10</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>488</number><title>MUC Token Invite</title><abstract>This specification provides a way to generate tokens to invite users to a MUC room.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>muc-token-invite</shortname><tags><tag>muc</tag><tag>token</tag><tag>invite</tag></tags><last-revision><date>2024-03-11</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>489</number><title>Reporting Account Affiliations</title><abstract>This specification documents a way for an XMPP server to report to other entities the relationship it has with a user on its domain.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>raa</shortname><last-revision><date>2024-03-11</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>490</number><title>Message Displayed Synchronization</title><abstract>This specification allows multiple clients of the same user to synchronize the displayed state of their chats.</abstract><type>Standards Track</type><status>Draft</status><approver>Council</approver><shortname>mds</shortname><last-revision><date>2024-11-20</date><version>1.0.1</version><initials>egp</initials><remark>* Fix some examples, and their indentation.
* Add the XML Schema.</remark></last-revision><sig>Standards</sig><lastcall>2024-10-31</lastcall></xep><xep accepted="true"><number>491</number><title>WebXDC</title><abstract>This document defines an XMPP protocol extension to communicate WebXDC widgets and their state updates.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>webxdc</shortname><last-revision><date>2024-10-17</date><version>0.1.3</version><initials>spw</initials><remark>* Clarifications and wording
* Better references for WebXDC spec</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>492</number><title>Chat notification settings</title><abstract>This document defines an XMPP protocol extension to synchronise per-chat notification settings across different clients.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>notification-settings</shortname><last-revision><date>2024-07-01</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>493</number><title>OAuth Client Login</title><abstract>This specification details how a third-party can be securely granted access to an XMPP account without exposing the account credentials, using OAuth.</abstract><type>Informational</type><status>Experimental</status><approver>Council</approver><shortname>tsa</shortname><last-revision><date>2024-09-17</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>494</number><title>Client Access Management</title><abstract>This specification details how an XMPP account owner can view and control which applications and services have access to their account.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>cam</shortname><last-revision><date>2024-09-17</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>495</number><title>Happy Eyeballs</title><abstract>When a server's IPv4 path and protocol are working, but the server's IPv6 path and protocol are not working, a dual-stack application that initiates a connect experiences significant connection delay compared to an IPv4-only application. This is undesirable because it causes the dual-stack initiating entity to have a worse user experience. This XEP defines how IETF's 'Happy Eyeballs' algorithm requirements that reduce this user-visible delay are applied to XMPP.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><last-revision><date>2024-10-17</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>* Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>496</number><title>Pubsub Node Relationships</title><abstract>This specification describes how to establish links between pubsub nodes, allowing for optional hierarchical organization.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-relationships</shortname><last-revision><date>2024-11-20</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>497</number><title>Pubsub Extended Subscriptions</title><abstract>This specification extends the XMPP PubSub protocol by introducing mechanisms for users to subscribe to an entire node hierarchy or to receive notifications on node metadata updates.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-ext-sub</shortname><last-revision><date>2024-11-20</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>498</number><title>Pubsub File Sharing</title><abstract>This specification explains how to share files and optionally include directory structures similar to filesystems over XMPP Pubsub. It leverages XMPP Pubsub to enable notifications about file changes and manage permissions, providing users with real-time updates and control mechanisms. An optional mechanism is also specified for managing uploaded files.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-relationships</shortname><last-revision><date>2024-11-20</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>499</number><title>Pubsub Extended Discovery</title><abstract>This specification extends the discovery requests used with the XMPP PubSub protocol by introducing mechanisms to discover linked nodes, descendants, or metadata.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>pubsub-ext-disco</shortname><last-revision><date>2024-11-20</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>500</number><title>MUC Slow Mode</title><abstract>This specification describes a way to rate limit messages a single user can send to a MUC room. It includes room configuration option, and how servers and clients can handle such a feature.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>muc-slow-mode</shortname><tags><tag>muc</tag><tag>slow mode</tag></tags><last-revision><date>2024-12-03</date><version>0.1.1</version><initials>jl</initials><remark>Include first feedbacks</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>501</number><title>Pubsub Stories</title><abstract>This specification defines a way of publishing Stories over XMPP.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>ps</shortname><last-revision><date>2024-12-20</date><version>0.2.0</version><initials>tj</initials><remark>Add pubsub#item_expire in the node configuration</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>502</number><title>MUC Activity Indicator</title><abstract>This specification provides querying entities an approximate indication of the level of activity in a given XEP-0045 Multi-User Chat room.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>muc-activity</shortname><last-revision><date>2024-12-23</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>Promoted to Experimental</remark></last-revision><sig>Standards</sig></xep><xep accepted="true"><number>503</number><title>Server-side spaces</title><abstract>This document defines an XMPP protocol to cluster several groupchat rooms together.</abstract><type>Standards Track</type><status>Experimental</status><approver>Council</approver><shortname>spaces</shortname><last-revision><date>2025-03-11</date><version>0.1.0</version><initials>XEP Editor: dg</initials><remark>Promoted to Experimental</remark></last-revision><sig> Standards</sig></xep><xep accepted="false"><number>xxxx</number><title>Account Management</title><abstract>This specification provides a collection of stream features meant to manage one's account, in particular for account registration, deletion and change of password.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><supersedes><spec>XEP-0077</spec></supersedes><last-revision><date>2011-07-17</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>account-management</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Authorization Tokens</title><abstract>This document defines an XMPP protocol extension for issuing authentication tokens to client applications and provides methods for managing &#1089;lient connections.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>xabber-tokens</shortname><last-revision><date>2019-09-11</date><version>0.0.1</version><initials>ag/an</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>auth-tokens</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Automatic Trust Management (ATM)</title><abstract>This document specifies a way to automatically manage the trust in public long-term keys used by end-to-end encryption protocols.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>ATM</shortname><last-revision><date>2020-11-05</date><version>0.0.1</version><initials>melvo</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>automatic-trust-management</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Automatic Trust Transfer (ATT)</title><abstract>ATT specifies an automatic transfer of trust in public identity keys used by the end-to-end encryption protocol OMEMO.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2019-03-22</date><version>0.0.1</version><initials>mk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>automatic-trust-transfer</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Jingle Audio/Video Conferences</title><abstract>This specification defines a way to hold multiparty conferences with an SFU via Jingle.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>av-conferences</shortname><last-revision><date>2024-07-29</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>av_conferences</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Improving Baseline Security in XMPP</title><abstract>This document describes a number of concrete and effective mechanisms for offering significant security enhancements to XMPP, with broad applicability.</abstract><type>Humorous</type><status>ProtoXEP</status><approver>Editor</approver><shortname>security-theatre</shortname><last-revision><date>2019-04-01</date><version>0.0.1</version><initials>cd/lg</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>baseline-security</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Bidirectional Server-to-Server Connections</title><abstract>This specification defines a protocol for using server-to-server connections in a bidirectional way such that stanzas are sent and received on the same TCP connection.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-09-13</date><version>0.0.2</version><initials>dwd</initials><remark>belated run-over pre-publication
Added notes on authentication</remark></last-revision><sig>Standards</sig><proto-name>bidi</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Body Markup Hints</title><abstract>This document specifies hints about the markup language used in elements.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>bmh</shortname><last-revision><date>2017-10-14</date><version>0.0.1</version><initials>fs</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>bmh</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Bookmark Pinning</title><abstract>This document defines an XMPP protocol extension to allow users to pin PEP Native Bookmarks.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>bookmarkspinning</shortname><last-revision><date>2020-05-17</date><version>0.0.1</version><initials>am</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>bookmark-pinning</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Bookmarks Conversion</title><abstract>This specification describes a method to migrate to PEP based bookmarks without loosing compatibility with client that still use Private XML.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>bookmarks-conversion</shortname><last-revision><date>2018-09-18</date><version>0.1.0</version><initials>dg</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>bookmarks-conversion</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Buddycloud Channels</title><abstract>This document describes a profile and conventions for usage of the PubSub protocol in the context of a new type of communication.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2014-04-29</date><version>0.0.2</version><initials>sdt</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>buddycloud-channels</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Simple Buttons</title><abstract>This specification provides a way to send simple buttons.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2018-09-30</date><version>0.0.2</version><initials>ka</initials><remark>Polishing preparing for submission</remark></last-revision><sig>Standards</sig><proto-name>buttons</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Calendaring Extensions to Publish-Subscribe</title><abstract>This specification defines calendaring extensions to Publish-Subscribe for the purposes of group calendaring and scheduling between "Calendar Users" (CUs), accessing, managing, and sharing calendaring and scheduling information on a Calendar Server, and a mechanism for alarm notifications.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname /><last-revision><date>2009-02-14</date><version>0.0.3.1</version><initials>kh</initials><remark>Added XML schema; fixed a number of minor issues.</remark></last-revision><sig>Standards</sig><proto-name>calendaring</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Call Invites</title><abstract>This document defines how to invite someone to a call and how to respond to the invite.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>call-invites</shortname><last-revision><date>2022-01-01</date><version>0.0.1</version><initials>nw/mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>call-invites</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Atomically Compare-And-Publish PubSub Items</title><abstract>This specification provides a mechanism to atomically Compare-And-Publish items to a PubSub node.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>cap</shortname><last-revision><date>2017-10-06</date><version>0.0.3</version><initials>fs</initials><remark>Use a custom item value (CAP-V).</remark></last-revision><sig>Standards</sig><proto-name>cap</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Message Carbons</title><abstract>In order to keep all IM clients for a user engaged in a conversation, outbound messages are carbon-copied to all interested resources.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>carbons</shortname><supersedes><spec>XEP-0259</spec></supersedes><last-revision><date>2010-02-25</date><version>0.0.1</version><initials>jjh</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>carbons</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Channel Binding Pseudomechanisms</title><abstract>A method for advertising and negotiating types of channel binding supported by SCRAM based SASL mechanisms.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pseudomechanisms</shortname><last-revision><date>2020-05-01</date><version>0.0.1</version><initials>ssw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>cb-pseudomechanisms</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Client Key Support</title><abstract>This specification defines an XMPP binding of the supporting functions for the CLIENT-KEY SASL mechanism.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>client-key</shortname><last-revision><date>2018-01-08</date><version>0.0.1</version><initials>dwd</initials><remark>First draft</remark></last-revision><sig>Standards</sig><proto-name>client-key</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Client State Indication</title><abstract>This document defines a way for the client to indicate its active/inactive state.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2014-08-14</date><version>0.0.1</version><initials>mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>client-state-notification</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Customizable Message Routing</title><abstract>This specification specifies customizable behavior of RFC 6121 section 8.5.2.1.1 to allow various message routing algorithms (e.g. for load balancing).</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2014-09-22</date><version>0.0.1</version><initials>fs</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>cmr</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Compatibility Fallbacks</title><abstract>This document defines a way to indicate that a specific part of the body only serves as fallback and which specification the fallback is for.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>compat</shortname><last-revision><date>2022-01-01</date><version>0.0.1</version><initials>nw/mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>compatibility-fallback</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Content Rating Labels</title><abstract>This specification provides a wire format in the form of a Service Discovery extension to allow services of various kinds to publish information about the kind of content they allow and/or endorse on their platform.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>crl</shortname><last-revision><date>2021-03-03</date><version>0.0.1</version><initials>jsc</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>content-ratings</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Content Types in Messages</title><abstract>This specification describes a generic method whereby content in messages can be tagged as having a specific Internet Content Type. It also provides a method for sending the same content using different content types, as a fall-back mechanism when communicating between clients having different content type support.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>content</shortname><last-revision><date>2016-01-15</date><version>0.0.1</version><initials>pw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>content-types</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Compliance Suites 2019</title><abstract>This document defines XMPP protocol compliance levels.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>CS2019</shortname><supersedes><spec>XEP-0378</spec></supersedes><last-revision><date>2018-12-08</date><version>0.0.1</version><initials>jsc</initials><remark>First draft based on XEP-0378.</remark></last-revision><sig>Standards</sig><proto-name>cs-2019</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Compliance Suites 2020</title><abstract>This document defines XMPP protocol compliance levels.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>CS2020</shortname><supersedes><spec>XEP-0412</spec></supersedes><last-revision><date>2018-12-08</date><version>0.0.1</version><initials>jsc</initials><remark>First draft based on XEP-0412. Non-editorial Changes:
* Added "Future Development" section</remark></last-revision><sig>Standards</sig><proto-name>cs-2020</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Compliance Suites 2021</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>CS2021</shortname><supersedes><spec>XEP-0423</spec></supersedes><last-revision><date>2020-09-02</date><version>0.0.1</version><initials>gl</initials><remark>First draft based on XEP-0423.</remark></last-revision><sig>Standards</sig><proto-name>cs-2021</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Compliance Suites 2022</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>CS2022</shortname><supersedes><spec>XEP-0443</spec></supersedes><last-revision><date>2021-02-03</date><version>0.0.1</version><initials>sp</initials><remark>First draft based on XEP-0443.</remark></last-revision><sig>Standards</sig><proto-name>cs-2022</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Compliance Suites 2023</title><abstract>This document defines XMPP application categories for different use cases (Core, Web, IM, and Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>CS2023</shortname><supersedes><spec>XEP-0459</spec></supersedes><last-revision><date>2023-01-25</date><version>0.0.1</version><initials>gl</initials><remark>First draft based on XEP-0459.</remark></last-revision><sig>Standards</sig><proto-name>cs-2023</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Presence Decloaking</title><abstract>This specification defines an XMPP protocol extension that enables a user to send directed presence with a request for the target to reciprocate.</abstract><type>Standards track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-01-17</date><version>0.0.2</version><initials>psa</initials><remark>Rewrote the introduction, clarified the security considerations, requested issuance of an appropriate URN from the XMPP Registrar.</remark></last-revision><sig>None</sig><proto-name>decloak</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Disco Feature Attachment</title><abstract>This specification provides a way to indicate that a feature is implemented for a specific namespace</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>dfa</shortname><last-revision><date>2021-07-22</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>disco-feature-attachment</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Distributed Multi-User Chat</title><abstract>This document defines methods for distributing Multi-User Chat (MUC) rooms across multiple services.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>dmuc</shortname><last-revision><date>2010-02-05</date><version>0.0.2</version><initials>psa</initials><remark>Simplified the protocol to use a master-slave approach; modified terminology.</remark></last-revision><sig>Standards</sig><proto-name>distributedmuc</proto-name></xep><xep accepted="false"><number>xxxx</number><title>DMUC3: Distributed MUC</title><abstract>This document provides a protocol for reducing the bandwidth cost of local users contributing to a remote MUC over a constrained link through a local mirror of the MUC room.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>DMUC</shortname><last-revision><date>2011-01-25</date><version>0.0.1</version><initials>waf</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>dmuc3</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Domain Name Assertions</title><abstract>An application-level approach to asserting and proving the delegated ownership of a domain name for server-to-server XMPP federation.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>dna</shortname><supersedes><spec>XEP-0220</spec><spec>XEP-0238</spec></supersedes><last-revision><date>2009-07-27</date><version>0.0.1</version><initials>jjh</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>dna</proto-name></xep><xep accepted="false"><number>xxxx</number><title>DOAP usage in XMPP</title><abstract>This specification defines how XMPP projects can provide a machine-readable description of their abilities, and how external entities can interact with it.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2021-01-10</date><version>0.0.1</version><initials>egp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>doap-usage-in-xmpp</proto-name></xep><xep accepted="false"><number>xxxx</number><title>DNS Queries over XMPP (DoX)</title><abstract>This specification defines an XMPP protocol extension for sending DNS queries and getting DNS responses over XML streams. Each DNS query-response pair is mapped into an IQ exchange.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>dox</shortname><last-revision><date>2019-03-11</date><version>0.0.1</version><initials>tjb</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>dox</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Design Considerations for Digital Signatures in XMPP</title><abstract>This document discusses considerations for the design of Digital Signatures in XMPP, including use cases and requirements. The document also discusses various ways XML Digital Signatures could be used in XMPP.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><shortname>xmpp-dsig-design</shortname><last-revision><date>2009-08-20</date><version>0.0.090820</version><initials>kdz</initials><remark>Proto-XEP draft.</remark></last-revision><sig>Standards</sig><proto-name>dsig-design</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Digital Signatures in XMPP</title><abstract>This document provides a technical specification for Digital Signatures in the Extensible Messaging and Presence Protocol (XMPP).</abstract><type>Technical Specification</type><status>Proto</status><approver>Council</approver><last-revision><date>2010-03-10</date><version>0.0</version><initials>kdz</initials><remark>Proto-XEP draft.</remark></last-revision><sig>Standards</sig><proto-name>dsig</proto-name></xep><xep accepted="false"><number>xxxx</number><title>E2E Authentication in XMPP: CA Requirements</title><abstract>This specification defines requirements for certificate authorities issuing X.509 certificates for e2e authentication in XMPP.</abstract><type>Procedural</type><status>ProtoXEP</status><approver>Board</approver><last-revision><date>2019-02-08</date><version>0.0.1</version><initials>evk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>eax-car</proto-name></xep><xep accepted="false"><number>xxxx</number><title>E2E Authentication in XMPP: Certificate Issuance and Revocation</title><abstract>This specification defines a way for a certificate authority to serve certificate signing requests via XMPP in order to issue X.509 certificates for the use in end-to-end and c2s SASL EXTERNAL authentication.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2019-03-11</date><version>0.0.1</version><initials>evk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>eax-cir</proto-name></xep><xep accepted="false"><number>xxxx</number><title>E2E Authentication in XMPP</title><abstract>This specification describes how X.509 certificates can be used for end-to-end authentication in XMPP.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2019-02-08</date><version>0.0.1</version><initials>evk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>eax</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Ephemeral Messages</title><abstract>This specification encourages a shift in privacy settings wrt. logging policies.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2022-04-16</date><version>0.0.2</version><initials>pep</initials><remark>Resubmit with some changes.</remark></last-revision><sig>Standards</sig><proto-name>ephemeral-messages-v2</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Encryption for stateless file sharing</title><abstract>This specification provides a protocol for sharing encrypted files using the stateless file sharing protocol (XEP-xxxx).</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>esfs</shortname><last-revision><date>2020-11-10</date><version>0.0.1</version><initials>lmw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>esfs</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Events</title><abstract>This specification describe how to handle events with XMPP.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>events</shortname><last-revision><date>2022-09-08</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>events</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Extended Channel Search</title><abstract>This specification provides a standardised protocol to search for public group chats. In contrast to XEP-0030 (Service Discovery), it works across multiple domains and in contrast to XEP-0055 (Jabber Search) it more clearly handles extensibility.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>ECS</shortname><last-revision><date>2020-02-19</date><version>0.0.1</version><initials>jsc</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>extended-channel-search</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Fallback Indication</title><abstract>This specification proposes a mechanism by which message bodies can be marked as being purely for fallback purposes, and therefore to be ignored by intermediaries and anything that understands the remainder of the message.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>fallback</shortname><last-revision><date>2019-12-30</date><version>0.0.1</version><initials>dwd</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>fallback</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Message Fastening</title><abstract>This specification defines a way for payloads on a message to be marked as being logically fastened to a previous message.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>fasten</shortname><last-revision><date>2019-09-04</date><version>0.0.1</version><initials>ks</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>fasten</proto-name></xep><xep accepted="false"><number>xxxx</number><title>File metadata element</title><abstract>This specification defines a generic file metadata element to be used in other specifications.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>file-metadata</shortname><last-revision><date>2020-11-03</date><version>0.0.1</version><initials>lmw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>file-metadata</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Federated MUC for constrained environments</title><abstract>This document provides a protocol for reducing the bandwidth cost of local users contributing to a remote MUC over a constrained link through local proxying of the MUC room.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>FMUC</shortname><last-revision><date>2010-05-24</date><version>0.0.1</version><initials>kis</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>fmuc</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stanza Forwarding</title><abstract>This specification defines best practices for delivery of XMPP stanzas that are forwarded from one address to another.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>forwarding</shortname><last-revision><date>2009-04-10</date><version>0.0.5</version><initials>psa</initials><remark>Changed service discovery feature to urn:xmpp:forwarding:0 in compliance with XMPP Registrar processes.</remark></last-revision><sig>Standards</sig><proto-name>forwarding-delivery</proto-name></xep><xep accepted="false"><number>xxxx</number><title>File Sharing Notifications</title><abstract>This specification provides a notification protocol for information about ongoing file uploads and media creation by the user.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2018-08-21</date><version>0.0.4</version><initials>lnj</initials><remark>Add upload-finished state, minor improvements.</remark></last-revision><sig>Standards</sig><proto-name>fsn</proto-name></xep><xep accepted="false"><number>xxxx</number><title>File Transfer Metadata</title><abstract>An extension to XEP-0096 and XEP-0234 to design a way of adding arbitrary data to file transfer offers.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2011-11-11</date><version>0.0.1</version><initials>jl</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>ft-metadata</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Full Text Search in MAM</title><abstract>This specification proposes a field in the MAM form for full text searching.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>fulltextmam</shortname><last-revision><date>2020-01-21</date><version>0.0.1</version><initials>dwd</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>fulltext</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Gateway Relayed Encryption</title><abstract>This specification describes a mechanism for end-to-end encryption with gateways that is compatible with third-party networks.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>gre</shortname><tags><tag>gre</tag><tag>e2ee</tag></tags><last-revision><date>2025-01-12</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>gateway-relayed-encryption</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Best practices for GDPR compliant deployment of XMPP</title><abstract>This informational XEP provides information on deploying XMPP in way that is compliant with the General Data Protection Regulation (GDPR) of the European Union.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2018-05-22</date><version>0.0.1</version><initials>wt</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>gdpr</proto-name></xep><xep accepted="false"><number>xxxx</number><title>GRE Encrypter: OpenPGP</title><abstract>This GRE Encrypter uses OpenPGP to encrypt payload.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>gre-encrypter-openpgp</shortname><tags><tag>gre</tag><tag>encrypter</tag></tags><last-revision><date>2025-01-12</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>gre-encrypter-openpgp</proto-name></xep><xep accepted="false"><number>xxxx</number><title>GRE Formatter: MIME</title><abstract>This GRE Formatter uses Multipurpose Internet Mail Extensions (MIME) to format payload.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>gre-formatter-mime</shortname><tags><tag>gre</tag><tag>formatter</tag></tags><last-revision><date>2025-01-12</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>gre-formatter-mime</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Connections across HTTPS (HACX)</title><abstract>This specification defines a procedure to look up various connection methods for an XMPP server over HTTPS, with a focus on censorship resistance.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2018-05-16</date><version>0.0.2</version><initials>tjb</initials><remark>Fix requirements, editing, add alternatives.</remark></last-revision><sig>Standards</sig><proto-name>hacx</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Cryptographic Hash Function Recommendations for XMPP</title><abstract>This document provides recommendations for the use of cryptographic hash functions in XMPP protocol extensions.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><shortname>hashrecs</shortname><last-revision><date>2019-01-13</date><version>0.0.1</version><initials>psa</initials><remark>Split from XEP-0300.</remark></last-revision><sig>Standards</sig><proto-name>hash-recommendations</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Host Meta 2 - One Method To Rule Them All</title><abstract>This document defines an XMPP Extension Protocol for extending XEP-0156 by modifying the JSON Web Host Metadata Link format to support discovering all possible XMPP connection methods, for c2s and s2s</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>connections-v2</shortname><supersedes><spec>XEP-0156</spec><spec>RFC 7711</spec></supersedes><last-revision><date>2023-11-19</date><version>0.0.1</version><initials>tjb</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>host-meta-2</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pre-Authenticated In-Band Registration</title><abstract>This document extends the In-Band-Registration protocol to use invitation tokens, e.g. for registering accounts on non-public servers.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>ibr-token</shortname><last-revision><date>2020-10-28</date><version>0.1.0</version><initials>gl</initials><remark>First version based on XEP-0401.</remark></last-revision><sig>Standards</sig><proto-name>ibr-token</proto-name></xep><xep accepted="false"><number>xxxx</number><title>IM Routing-NG</title><abstract>This specification provides a new set of routing rules for modern instant messaging.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>IM-NG</shortname><last-revision><date>2018-03-29</date><version>0.0.2</version><initials>kis</initials><remark>Fix various slips, mention reflection.</remark></last-revision><sig>Standards</sig><proto-name>im-ng</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Inbox</title><abstract>This specification proposes a mechanism by which clients can find a list of ongoing conversations and their state.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>inbox</shortname><last-revision><date>2019-12-30</date><version>0.0.1</version><initials>dwd</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>inbox</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Incident Reporting</title><abstract>This specification defines methods for incident reporting among XMPP server deployments.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-04-30</date><version>0.0.3</version><initials>psa</initials><remark>Per Council feedback, moved server rosters to a separate specification.</remark></last-revision><sig>Standards</sig><proto-name>incident-reporting</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Instant Gaming</title><abstract>This document defines an XMPP protocol extension for serverless instant gaming in a one-to-one context.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-03-14</date><version>0.0.1</version><initials>tg</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>instant-gaming</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Internet of Things - Events</title><abstract>This specification describes an architecture based on the XMPP protocol whereby Things can subscribe to events from other Things based on sensor data available.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>iot-events</shortname><last-revision><date>2014-08-13</date><version>0.0.1</version><initials>pw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>iot-events</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Instant Stream Resumption</title><abstract>This specification introduces a mechanism for instant stream resumption, based on Stream Management (XEP-0198), allowing XMPP entities to instantaneously resume an XMPP stream.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>isr</shortname><last-revision><date>2017-11-30</date><version>0.0.5</version><initials>fs</initials><remark>Minor changes</remark></last-revision><sig>Standards</sig><proto-name>isr-sasl2</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Instant Stream Resumption</title><abstract>This specification introduces a mechanism for instant stream resumption, based on Stream Management (XEP-0198), allowing XMPP entities to instantaneously resume an XMPP stream.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>isr</shortname><last-revision><date>2016-03-11</date><version>0.0.2</version><initials>fs</initials><remark>Second draft.</remark></last-revision><sig>Standards</sig><proto-name>isr</proto-name></xep><xep accepted="false"><number>xxxx</number><title>JID Mention</title><abstract>This specification provides a way for an entity to mention a jid</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2016-01-16</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>jid-mention</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Jingle In-Band Bytestreams Transport</title><abstract>This specification defines a Jingle transport method that results in sending data via the In-Band Bytestreams (IBB) protocol defined in XEP-0047. Essentially this transport method reuses XEP-0047 semantics for sending the data and defines native Jingle methods for starting and ending an IBB session.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>jingle-ibb</shortname><last-revision><date>2009-02-10</date><version>0.0.1</version><initials>psa</initials><remark>Rough draft.</remark></last-revision><sig>Standards</sig><proto-name>jingle-ibb</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Jingle Relay Nodes</title><abstract>This documents specifies how Jingle Clients can interact with Jingle Relay Nodes Services and how XMPP entities can provide, search and list available Jingle Relay Nodes.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>Jingle Nodes</shortname><last-revision><date>2009-12-17</date><version>0.0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>jingle-nodes</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Codecs for Jingle RTP Sessions</title><abstract>This document describes implementation considerations related to voice and video codecs for use in Jingle RTP sessions.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-04-04</date><version>0.0.4</version><initials>psa</initials><remark>Clarified status of H.264.</remark></last-revision><sig>Standards</sig><proto-name>jingle-rtp-codecs</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Mandatory-to-Implement Technologies for Jingle RTP Sessions</title><abstract>This specification defines mandatory-to-implement technologies for Jingle RTP sessions, in particular codecs for voice and video chat.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-03-04</date><version>0.0.2</version><initials>psa</initials><remark>Added more information about video codecs.</remark></last-revision><sig>Standards</sig><proto-name>jingle-rtp-mti</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Jingle SOCKS5 Bytestreams Transport Method</title><abstract>This specification defines a Jingle transport method that results in sending data via the SOCKS5 Bytestreams (S5B) protocol defined in XEP-0065. Essentially this transport method reuses XEP-0065 semantics for sending the data and defines native Jingle methods for starting and ending an S5B session.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>jingle-s5b</shortname><last-revision><date>2009-02-18</date><version>0.0.3</version><initials>psa</initials><remark>Clarified order of events to be consistent with raw-udp and ice-udp.</remark></last-revision><sig>Standards</sig><proto-name>jingle-s5b</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Jingle SDP Content</title><abstract>This specification defines a Jingle application type for transport the Session Description Protocol (SDP) over Jingle.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>jingle-sdp</shortname><last-revision><date>2013-09-05</date><version>0.0.1</version><initials>ph</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>jingle-sdp</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Transport Layer Security</title><abstract>This document specifies the XMPP Transport Layer Security (XTLS) protocol. XTLS, which provides communications privacy for the Extensible Messaging and Presence Protocol (XMPP), enables XMPP applications to communicate in a way that is designed to prevent eavesdropping, tampering, and forgery of XML stanzas. XTLS is based on Transport Layer Security (TLS) and integrated as security layer into Jingle. The protocol can be used for secure end-to-end messages as well as any other Jingle application like file file transfer.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-02-21</date><version>0.0.4</version><initials>dm</initials><remark>Improved the documentation about exchanging passwords and certificates.</remark></last-revision><sig>Standards</sig><proto-name>jingle-xtls</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Use of ZRTP in Jingle RTP Sessions</title><abstract>This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-02-24</date><version>0.0.2</version><initials>psa</initials><remark>Defined dedicated namespace for the zrtp-hash element to improve service discovery and handling of session-info message; clarified protocol flow and security considerations.</remark></last-revision><sig>Standards</sig><proto-name>jingle-zrtp</proto-name></xep><xep accepted="false"><number>xxxx</number><title>JSON Content Type support</title><abstract>This specification defines JavaScript Object Notation (JSON) use in XMPP service.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-05-07</date><version>0.0.1</version><initials>MiH</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>json</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Linked Process Protocol</title><abstract>Linked Process is a protocol for distributed computing that facilitates the creation of an Internet-scale, general-purpose compute cloud. Any computing device with an Internet connection can consume and/or provide computing resources in a Linked Process cloud. Resource consumption occurs when a device migrates arbitrary code to another device for execution. Linked Process is applicable where it is necessary for a resource consumer to define the means by which a provider's resources are utilized.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-09-18</date><version>0.0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>lop</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MAM Fastening Collation</title><abstract>This specification proposes a mechanism by which MAM results containing fastenings can be collated effectively.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>mamfc</shortname><last-revision><date>2019-12-19</date><version>0.0.1</version><initials>dwd</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>mamfc</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Mediated Information eXchange (MIX)</title><abstract>This document defines Mediated Information eXchange (MIX), an XMPP protocol extension for the exchange of information among multiple participants through a mediating service. The protocol can be used to model group communication applications such as chatrooms, although with greater flexibility and extensibility than existing groupchat technologies such as Multi-User Chat (MUC). Although MIX supports standard groupchat features such as discussion topics and invitations, and also defines a strong access control model similar to that of MUC, it enables users to participate without sharing presence, allows communication of any structured data (not only textual messages), reuses Publish-Subscribe so that users can receive only the information formats in which they are interested, and reuses Message Archive Management (MAM) to provide more robust storage and archiving.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>MIX</shortname><last-revision><date>2015-10-12</date><version>0.0.1</version><initials>kis/psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>mix</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP on Mobile Devices</title><abstract>This document provides background information for XMPP implementors concerned with mobile devices operating in a cellular network such as 3G.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-07-13</date><version>0.0.1</version><initials>dwd</initials><remark>First draft. Also John's birthday.</remark></last-revision><sig>Standards</sig><proto-name>mobile</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Moved</title><abstract>This document defines an XMPP protocol extension that enables a user to inform its contacts about a change in JID.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>moved</shortname><last-revision><date>2010-06-09</date><version>0.0.7</version><initials>tp</initials><remark>Modified syntax to use 'old' and 'new' attributes.</remark></last-revision><sig>Standards</sig><proto-name>moved</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Moved 2.0</title><abstract>This specification details a way for a user to notify their contacts about an account move.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2021-06-05</date><version>0.0.1</version><initials>mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>moved2</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Activity Indicator</title><abstract>This specification provides querying entities an approximate indication of the level of activity in a given XEP-0045 Multi-User Chat room.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2024-11-29</date><version>0.0.1</version><initials>jsc</initials><remark>Initial submission.</remark></last-revision><sig>Standards</sig><proto-name>muc-activity</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Multi-User Chat Administration</title><abstract>This specification defines how to administer Multi-User Chat rooms and services using Ad-Hoc Commands.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2012-09-25</date><version>0.0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>muc-admin</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Affiliations Versioning</title><abstract>This specification provides a way to reduce the amount of queries necessary to stay up-to-date with affiliations in a MUC room.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2022-02-12</date><version>0.0.1</version><initials>pep</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>muc-affiliations-versioning</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Avatars</title><abstract>This specification describes how to publish and retrieve avatars in rooms.</abstract><type>Historical</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2023-02-15</date><version>0.0.3</version><initials>egp</initials><remark>Restore to the first revision, and republish to the Historical track.</remark></last-revision><sig>Standards</sig><proto-name>muc-avatars</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Multi-User Chat Light</title><abstract>This specification provides a presence-less standard for Multi-User Chats. Its feature set is a response to mobile XMPP applications needs and specific environment.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2015-10-29</date><version>0.0.1</version><initials>PN</initials><remark>First full version.</remark></last-revision><sig>Standards</sig><proto-name>muc-light</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Mention Notifications</title><abstract>This specification documents how a user may be informed when they're mentioned in a MUC which they're not currently joined to.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2020-12-17</date><version>0.0.1</version><initials>jcb</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>muc-mention-notifications</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC presence versioning</title><abstract>This specification defines a versioning mechanism which reduces the amount of presence traffic in a XEP-0045 MUC</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>omnipresent-muc-affiliates</shortname><last-revision><date>2020-03-30</date><version>0.0.1</version><initials>jcb</initials><remark>First draft</remark></last-revision><sig>Standards</sig><proto-name>muc-presence-versioning</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Self-Ping (Schr&#246;dinger's Chat)</title><abstract>This protocol extension for XEP-0045 Multi User Chat allows clients to check whether they are still joined to a chatroom.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>muc-selfping</shortname><last-revision><date>2018-08-06</date><version>0.0.2</version><initials>gl</initials><remark>Add handling for another corner case, change title to Council&#8217;s liking</remark></last-revision><sig>Standards</sig><proto-name>muc-selfping</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Token Invite</title><abstract>This specification provides a way to generate tokens to invite users to a MUC room.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><tags><tag>muc</tag><tag>token</tag><tag>invite</tag></tags><last-revision><date>2023-08-15</date><version>0.0.1</version><initials>pep</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>muc-token-invite</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Muji</title><abstract>This specification defines an XMPP protocol extension for initiating and managing multiparty voice and video conferences within an XMPP MUC</abstract><type>Extension</type><status>ProtoXep</status><approver>Telepathy project</approver><shortname>muji</shortname><last-revision><date>2009-06-09</date><version>0.0.0.2</version><initials>sjoerd</initials><remark>Second rough draft.</remark></last-revision><sig>Standards</sig><proto-name>muji</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Multi-User Gaming</title><abstract>This document defines an XMPP protocol extension for multi-user gaming.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>mug</shortname><last-revision><date>2009-04-20</date><version>0.0.3</version><initials>gn</initials><remark>Added sections about entering non-anonymous, semi-anonymous and fully-anonymous rooms.</remark></last-revision><sig>Standards</sig><proto-name>multi-user_gaming</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Multi-stage IBR</title><abstract>This specification defines an augmentation of In-Band Registration to allow for multiple stages of user input.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2016-02-03</date><version>0.0.1</version><initials>spw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>multistage-ibr</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stanza Multiplexing</title><abstract>This spec provides a mechanism for multiplexing multiple virtual hosts over a single XMPP session.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>mux</shortname><supersedes><spec>XEP-0220</spec></supersedes><last-revision><date>2020-12-03</date><version>0.0.1</version><initials>ssw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>mux</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Chat notification settings</title><abstract>This document defines an XMPP protocol extension to synchronise per-chat notification settings across different clients.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>notification-settings</shortname><last-revision><date>2024-02-08</date><version>0.0.2</version><initials>nc</initials><remark>Update after discussions on the standards@ mailing list.</remark></last-revision><sig>Standards</sig><proto-name>notification-filter</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Notification Inbox</title><abstract>This document defines a protocol to manage a notification inbox for pending events.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>inbox</shortname><last-revision><date>2015-12-09</date><version>0.0.2</version><initials>XEP Editor (mam)</initials><remark>Updated contact information for Valerian Saliou.</remark></last-revision><sig>Standards</sig><proto-name>notification-inbox</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Namespace Versioning in urn:xmpp</title><abstract>This document describes the common practise of namespace versioning for the urn:xmpp URN namespace, and how this affects (and does not affect) the protocols which have such namespaces.</abstract><type>Informational</type><status>Experimental</status><approver>Council</approver><shortname>namespace</shortname><last-revision><date>2015-04-07</date><version>0.0.2</version><initials>dc</initials><remark>Noticed two conversations in two weeks. Must be time to reify this one. Added two new misconceptions; the author vs registrar one was mine.</remark></last-revision><sig>Standards</sig><proto-name>nsver</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Anonymous unique occupant identifiers for MUCs</title><abstract>This specification defines a method that allows clients to identify a MUC participant across reconnects and renames. It thus prevents impersonification of anonymous users.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>occupant-id</shortname><last-revision><date>2019-07-13</date><version>0.0.1</version><initials>mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>occupant-id</proto-name></xep><xep accepted="false"><number>xxxx</number><title>OMEMO Encrypted Jingle File Transfer</title><abstract>This specification defines a Jingle application for transfering encrypted files from one entity to another. The protocol is based on the regular Jingle File Transfer specification and diverges from that only in the description of the file.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2015-09-02</date><version>0.0.1</version><initials>dg</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>omemo-filetransfer</proto-name></xep><xep accepted="false"><number>xxxx</number><title>OMEMO Media sharing</title><abstract>An informal way of sharing media files despite limitations in the OMEMO encryption</abstract><type>Historical</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2021-01-10</date><version>0.0.2</version><initials>egp</initials><remark>* Resubmitted on the Historical track.
* Added a section on IANA considerations.</remark></last-revision><sig>Standards</sig><proto-name>omemo-media-sharing</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Order-By</title><abstract>This specification allows to change order of items retrieval in a Pubsub or MAM query</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2019-01-05</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>order-by</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Out-of-Band Stream Data</title><abstract>This specification defines how to send parts of an XML stream over a direct connection between peers. This allows to send large stanzas or binary data without blocking the XML stream for other stanzas.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-03-30</date><version>0.0.2</version><initials>dm</initials><remark>Simplify Example; Restrict Usage; Add abort</remark></last-revision><sig>Standards</sig><proto-name>outofband</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Best practices for password hashing and storage</title><abstract>This document outlines best practices for handling user passwords on the public Jabber network for both clients and servers.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><shortname>passwords</shortname><last-revision><date>2020-04-19</date><version>0.0.1</version><initials>ssw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>password-storage</proto-name></xep><xep accepted="false"><number>xxxx</number><title>User Avatar to vCard-Based Avatars Conversion</title><abstract>This specification describes a method for using PEP based avatars and vCard based avatars in parallel by having the user&#8217;s server do a conversion between the two.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pep-vcard-conversion</shortname><last-revision><date>2017-12-18</date><version>0.1.0</version><initials>dg</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pep-vcard-conversion</proto-name></xep><xep accepted="false"><number>xxxx</number><title>User Time Zone</title><abstract>This specification defines a payload format for communicating information about a user's time zone. The payload format is typically transported using the personal eventing protocol, a profile of XMPP publish-subscribe specified in XEP-0163.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2013-10-28</date><version>0.1</version><initials>lance</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>peptzo</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pre-auth Registration Key Generation and Validation</title><abstract>This specification updates XEP-0401 and XEP-0445 by specifying a shared format for the pre-authenticated registration token.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>preauth-token</shortname><last-revision><date>2021-06-06</date><version>0.0.1</version><initials>ssw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>preauth-ibr</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Problem Reporting</title><abstract>This specification defines methods for reporting of network problems between XMPP server deployments.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-04-13</date><version>0.0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>problem-reporting</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Attachments</title><abstract>This specification provides a way to attach elements to a pubsub item.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-attachments</shortname><last-revision><date>2022-07-11</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-attachments</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Caching Hints</title><abstract>This specification provides a way to get caching information from a Pubsub node</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-caching</shortname><last-revision><date>2021-07-19</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-caching-hints</proto-name></xep><xep accepted="false"><number>xxxx</number><title>OpenPGP for XMPP Pubsub</title><abstract>Specifies an OpenPGP for XMPP (XEP-0373) profile for the pubsub use case.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>oxps</shortname><last-revision><date>2022-10-12</date><version>0.0.6</version><initials>jp</initials><remark>* add forgotten "jid" and "node" attribute to &lt;revoke/&gt;
* clarify that &lt;openpgp/&gt; wrapper is used</remark></last-revision><sig>Standards</sig><proto-name>pubsub-encryption</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Extended Discovery</title><abstract>This specification extends the discovery requests used with the XMPP PubSub protocol by introducing mechanisms to discover linked nodes, descendants, or metadata.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-ext-disco</shortname><last-revision><date>2024-10-17</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-extended-discovery</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Extended Subscriptions</title><abstract>This specification extends the XMPP PubSub protocol by introducing mechanisms for users to subscribe to an entire node hierarchy or to receive notifications on node metadata updates.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-ext-sub</shortname><last-revision><date>2024-10-15</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-extended-subscription</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub File Sharing</title><abstract>This specification explains how to share files and optionally include directory structures similar to filesystems over XMPP Pubsub. It leverages XMPP Pubsub to enable notifications about file changes and manage permissions, providing users with real-time updates and control mechanisms. An optional mechanism is also specified for managing uploaded files.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-relationships</shortname><last-revision><date>2024-10-19</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-file-sharing</proto-name></xep><xep accepted="false"><number>xxxx</number><title>PubSub Type Filtering</title><abstract>This specification provides a way to filter PubSub nodes in a disco query.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2022-02-01</date><version>0.0.1</version><initials>edhelas, pep</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-filter</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Node Relationships</title><abstract>This specification describes how to establish links between pubsub nodes, allowing for optional hierarchical organization.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-relationships</shortname><last-revision><date>2024-10-09</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-node-relationships</proto-name></xep><xep accepted="false"><number>xxxx</number><title>PubSub Namespaces</title><abstract>This extension defines a new PubSub node attribute to specify the type of payload.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-ns</shortname><last-revision><date>2021-12-25</date><version>0.0.1</version><initials>mb</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-ns</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Public Subscriptions</title><abstract>This specification provides a way to make subscriptions to a node public</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pps</shortname><last-revision><date>2022-03-30</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-public-subscriptions</proto-name></xep><xep accepted="false"><number>xxxx</number><title>PubSub Server Information</title><abstract>This document defines a data format whereby basic information of an XMPP domain can be expressed and exposed over pub-sub.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>serverinfo</shortname><last-revision><date>2023-12-19</date><version>0.0.1</version><initials>gdk</initials><remark>* Initial version.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-server-info</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Signing: OpenPGP Profile</title><abstract>Specifies a pubsub signing profile for OpenPGP</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pss-ox</shortname><last-revision><date>2022-10-29</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-signing-openpgp</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Signing</title><abstract>Specifies a mechanism to sign pubsub items</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pubsub-signing</shortname><last-revision><date>2022-10-20</date><version>0.0.2</version><initials>jp</initials><remark>* replaced "signatory" term with the more commonly used "signer"
* added &lt;to/&gt; and &lt;time/&gt; elements (similar to XEP-0373)</remark></last-revision><sig>Standards</sig><proto-name>pubsub-signing</proto-name></xep><xep accepted="false"><number>xxxx</number><title>PubSub Since</title><abstract>This specification defines a publish-subscribe feature that enables a subscriber to automatically receive pubsub and PEP notifications since its last logout time.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2012-02-29</date><version>0.0.2</version><initials>psa</initials><remark>Addressed some feedback from the XMPP Council.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-since</proto-name></xep><xep accepted="false"><number>xxxx</number><title>PubSub Social Feed</title><abstract>This specification defines a way of publishing social content over XMPP.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>psf</shortname><supersedes><spec>XEP-0277</spec></supersedes><last-revision><date>2022-09-26</date><version>0.0.1</version><initials>tj</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-social-feed</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Targeted Encryption</title><abstract>Specifies a way to encrypt pubsub items for a restricted set of entities</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>pte</shortname><last-revision><date>2022-10-31</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-targeted-encryption</proto-name></xep><xep accepted="false"><number>xxxx</number><title>The 'xmpp.pubsub' URI Scheme</title><abstract>This document defines the format of Uniform Resource Identifiers (URIs) to identify nodes in the context of Publish-Subscribe services as well as items within the scope of such nodes.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2012-01-14</date><version>0.0.1</version><initials>kh</initials><remark>Initial draft.</remark></last-revision><sig>Standards</sig><proto-name>pubsub-uri</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Quality of Service</title><abstract>This specification describes a generic method whereby messages can be sent between clients using a predefined Quality of Service level.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>qos</shortname><last-revision><date>2015-11-12</date><version>0.0.1</version><initials>pw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>qos</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Quick Response</title><abstract>Quickly respond to automated messages.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2020-04-20</date><version>0.0.1</version><initials>th</initials><remark>Initial version</remark></last-revision><sig>Standards</sig><proto-name>quick-response</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Message Reactions</title><abstract>This specification defines a way for adding reactions to a message.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>reactions</shortname><last-revision><date>2019-07-14</date><version>0.0.1</version><initials>nw/mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>reactions</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Reminders</title><abstract>This specification provides a way to set up reminders.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2020-02-17</date><version>0.0.1</version><initials>mdvp</initials><remark>Initial version</remark></last-revision><sig>Standards</sig><proto-name>reminders</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Jingle Remote Control</title><abstract>This specification defines a way to remotely control a device using local peripheral inputs.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>remote-control</shortname><last-revision><date>2024-05-11</date><version>0.0.1</version><initials>jp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>remote-control</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Message Replies</title><abstract>This document defines a way to indicate that a message is a reply to a previous message.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>reply</shortname><last-revision><date>2022-01-01</date><version>0.0.1</version><initials>nw/mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>replies</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Entity Reputation</title><abstract>This specification defines an XMPP protocol extension for communicating the reputation of any entity on the network.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-01-11</date><version>0.0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>reputation</proto-name></xep><xep accepted="false"><number>xxxx</number><title>REST with XMPP</title><abstract>This specification defines how the Representational State Transfer (REST) architectural style can be applied to an XMPP overlay network. It specifies an XMPP protocol extension for accessing resources and transporting resource metadata and XML-REST encoded requests and responses between two XMPP entities.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2015-05-11</date><version>0.0.1</version><initials>as</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>rest</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Room Activity Indicators</title><abstract>This specification describes a lightweight mechanism for activity notifications in MUCs</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2020-04-13</date><version>0.0.1</version><initials>mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>room-activity-indicators</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Recipient Server Side Notifications Filtering</title><abstract>This specification defines a modern efficient way to deliver PubSub notifications.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2014-07-20</date><version>0.0.2</version><initials>sd</initials><remark>Updated based on Council feedback.</remark></last-revision><sig>Standards</sig><proto-name>rsf</proto-name></xep><xep accepted="false"><number>xxxx</number><title>S2S Components</title><abstract>This document describes a modernized method of connecting 'components' to a server, expressed as a profile of the existing standard server-to-server protocol.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>comp-s2s</shortname><supersedes><spec>XEP-0114</spec><spec>XEP-0225</spec></supersedes><last-revision><date>2015-01-20</date><version>0.0.1</version><initials>dwd</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>s2s-components</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Extensible SASL Profile</title><abstract>This document describes a replacement for the SASL profile documented in RFC 6120 which allows for greater extensibility.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sasl2</shortname><last-revision><date>2017-02-07</date><version>0.0.1</version><initials>dwd</initials><remark>* Initial Revision</remark></last-revision><sig>Standards</sig><proto-name>sasl2</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Sensor-Over-XMPP</title><abstract>This specification defines a payload format for communicating sensor and actuation information. The payload format is transported using the publish-subscribe mechanism described in XEP-0060.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sox</shortname><last-revision><date>2011-04-08</date><version>0.0.18</version><initials>css</initials><remark>Add data element to enclose transducerValue and transducerSetValue.</remark></last-revision><sig>Standards</sig><proto-name>sensors</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Server Rosters</title><abstract>This specification defines a convention for trust between XMPP server deployments.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-04-30</date><version>0.0.1</version><initials>ah/fj/psa/mr/mw</initials><remark>First draft, split from the incident reporting proposal.</remark></last-revision><sig>Standards</sig><proto-name>server-rosters</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Service Outage Status</title><abstract>This document defines an XMPP protocol extension that enables a server to communicate issues with the server to all users in a semantic manner.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2021-01-18</date><version>0.0.1</version><initials>mp</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>service-outage-status</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stateless file sharing</title><abstract>This specification describes a protocol for stateless asynchronous file sharing with integrity and transport flexibility. It allows clients to provide a good interoperable user experience in combination with Carbons and MAM.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sfs</shortname><last-revision><date>2020-11-10</date><version>0.0.1</version><initials>lmw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>sfs</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Shared BOSH</title><abstract>This specification defines an extension to BOSH that allows multiple clients to share the same underlying XMPP connection.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-05-13</date><version>0.0.1</version><initials>Jack</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>shared-bosh</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Server IP Check</title><abstract>This specification defines a simple XMPP extension that enables a client to discover its external IP address.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sic</shortname><last-revision><date>2009-03-10</date><version>0.0.2</version><initials>psa</initials><remark>Removed client inclusion of its IP address; added IPv6 example.</remark></last-revision><sig>Standards</sig><proto-name>sic</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stanza Interception and Filtering Technology</title><abstract>This specification defines an XMPP protocol extension that enables a client to exercise control over the XML stanzas it will receive from the server by instructing the server to intercept and filter inbound stanzas.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-08-14</date><version>0.0.8</version><initials>psa</initials><remark>Clarified service and feature discovery processes, error flows, and other small matters in the text.</remark></last-revision><sig>Standards</sig><proto-name>sift</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Special Interests Group End to End Encryption</title><abstract>This document proposes the formation of a Special Interest Group (SIG) within the XSF devoted to the development of end-to-end encryption within the context of XMPP.</abstract><type>Procedural</type><status>ProtoXEP</status><approver>Council</approver><shortname>SIG-E2EE</shortname><last-revision><date>2019-12-30</date><version>0.0.1</version><initials>ps</initials><remark>Initial published version.</remark></last-revision><sig>None</sig><proto-name>sige2ee</proto-name></xep><xep accepted="false"><number>xxxx</number><title>SIP/SDP Over XMPP (SoX)</title><abstract>This specification defines an XMPP protocol extension for communicating Session Description Protocol (SDP) data, along with relevant Session Initiation Protocol (SIP) headers. The SoX protocol is designed for use by XMPP-only endpoints that need to communicate raw SDP information (e.g., in WebRTC scenarios), not as a general-purpose replacement for the XMPP Jingle extensions.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2013-12-02</date><version>0.0.2</version><initials>psa</initials><remark>Clarified scope and intent of the protocol.</remark></last-revision><sig>Standards</sig><proto-name>sox</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Server-side spaces</title><abstract>This document defines an XMPP protocol to cluster several groupchat rooms together.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>spaces</shortname><last-revision><date>2025-02-23</date><version>0.0.1</version><initials>nc</initials><remark>Initial version.</remark></last-revision><sig> Standards</sig><proto-name>spaces</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Spim Markers and Reports</title><abstract>This document defines an XMPP protocol extension that enables XMPP entities to interact with spim filters by marking unsolicited or suspicious XMPP stanzas.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-09-13</date><version>0.1</version><initials>evk</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>spim</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stickers</title><abstract>This specification provides a protocol to send stickers and to create and share sticker packs.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>stickers</shortname><last-revision><date>2020-11-03</date><version>0.0.1</version><initials>lmw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>stickers</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Pubsub Stories</title><abstract>This specification defines a way of publishing Stories over XMPP.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>ps</shortname><last-revision><date>2024-12-03</date><version>0.0.1</version><initials>tj</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>stories</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Shared XML Editing</title><abstract>This specification defines a protocol that enables two or more endpoints to collaboratively edit an XML object. The protocol is intended for use mainly over the Extensible Messaging and Presence Protocol (XMPP), either by existing instant messaging clients or by specialized editing clients. However, the protocol could also be used over a direct TCP connection rather than over XMPP.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2010-06-08</date><version>0.0.10</version><initials>tp/psa</initials><remark>Updated Jingle namespaces, transport definitions, reason codes, and other syntax; improved feature discovery and session advertisement; updated namespace to be urn:xmpp:sxe:0 for future-compatibility.</remark></last-revision><sig>Standards</sig><proto-name>sxe</proto-name></xep><xep accepted="false"><number>xxxx</number><title>File Transfer Thumbnails</title><abstract>This specification defines a way for a client supply a preview image for a file transfer.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>thumbs</shortname><last-revision><date>2009-03-10</date><version>0.0.3</version><initials>ml</initials><remark>Split use-case section into "Introduction", "Requirements", and "Use case".</remark></last-revision><sig>Standards</sig><proto-name>thumbs</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Server-based Tic-tac-toe</title><abstract>This document defines how to play a Tic-tac-toe game over XMPP</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-03-14</date><version>0.0.1</version><initials>ak</initials><remark>First Draft.</remark></last-revision><sig>Standards</sig><proto-name>tictactoe-mug</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Tic-tac-toe</title><abstract>This document defines how to play a Tic-tac-toe game over XMPP</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2009-03-14</date><version>0.0.1</version><initials>tg</initials><remark>First Draft.</remark></last-revision><sig>Standards</sig><proto-name>tictactoe</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Token-based reconnection</title><abstract>This specification defines a token-based session authentication mechanism.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2016-02-16</date><version>0.0.2</version><initials>mp</initials><remark>Removed mention of OAuth from Abstract; removed mention of DIGEST-MD5.</remark></last-revision><sig>Standards</sig><proto-name>token-reconnection</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Terms of Services</title><abstract>This specification provides an in-band, unauthenticated way to request the Terms of Service of an XMPP service.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>TOS</shortname><last-revision><date>2018-05-22</date><version>0.0.1</version><initials>jwi</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>tos</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Multi-Factor Authentication with TOTP</title><abstract>This specification defines support for multi-factor authentication in terms of SASL2 Tasks based around the Time-based One Time Password mechanism.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>mfa</shortname><last-revision><date>2018-01-08</date><version>0.0.2</version><initials>dwd</initials><remark>So ABNF isn't well-formed XML, of course...</remark></last-revision><sig>Standards</sig><proto-name>totp-2fa</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Trust Messages</title><abstract>This document specifies a way to communicate the trust in public long-term keys used by end-to-end encryption protocols from one endpoint to another.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2020-02-15</date><version>0.0.1</version><initials>mk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>trust-messages</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Simple JSON Messaging</title><abstract>This specification proposes a simple mechanism by which applications can transfer data safely, without needing additional protocol design work. It is intended to provide a protocol that is trivial to implement and can be driven with a simple API.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>udt</shortname><last-revision><date>2020-02-13</date><version>0.0.2</version><initials>dwd</initials><remark>Have another crack at getting this through Council.
* Rename to a more obvious name
* Remove IQ
* Remove API, instead describe API requirements</remark></last-revision><sig>Standards</sig><proto-name>udt</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Two-factor user authentication with a shared secret</title><abstract>This document specifies a two-factor authentication mechanism to check if a XMPP account exists and if it is trying to use or access services or resources of certain device, application or service. Authentication mechanism is based on transmitting a password using Ad-Hoc Commands. Password is calculated from shared secret.</abstract><type>Standards Strack</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2013-12-19</date><version>0.0.1</version><initials>tuv</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>user-auth</proto-name></xep><xep accepted="false"><number>xxxx</number><title>User Rating</title><abstract>This specification provides for the rating element.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2016-05-21</date><version>0.0.1</version><initials>dsw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>userrating</proto-name></xep><xep accepted="false"><number>xxxx</number><title>WebSocket S2S</title><abstract>This specification defines a procedure to make s2s XMPP connections over WebSocket.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2022-06-13</date><version>0.0.1</version><initials>tjb</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>websocket-s2s</proto-name></xep><xep accepted="false"><number>xxxx</number><title>WebXDC</title><abstract>This document defines an XMPP protocol extension to communicate WebXDC widgets and their state updates.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>webxdc</shortname><last-revision><date>2024-06-05</date><version>0.0.1</version><initials>spw</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>webxdc</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Communicate &amp; Ask to AI</title><abstract>This document defines a protocol for asking questions to an artificial intelligence or requesting it to make predictions.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><tags><tag>template</tag></tags><last-revision><date>2023-03-13</date><version>0.0.1</version><initials>ae</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-ai</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Client Access Management</title><abstract>This specification details how an XMPP account owner can view and control which applications and services have access to their account.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>cam</shortname><last-revision><date>2024-08-20</date><version>0.0.1</version><initials>mjw</initials><remark>
</remark></last-revision><sig>Standards</sig><proto-name>xep-client-access-management</proto-name></xep><xep accepted="false"><number>xxxx</number><title>SASL SCRAM Downgrade Protection</title><abstract>This specification provides a way to secure the SASL and SASL2 handshakes against method and channel-binding downgrades.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>SSDP</shortname><last-revision><date>2022-10-11</date><version>0.0.1</version><initials>tm</initials><remark>Initial version.</remark></last-revision><sig>Standards</sig><proto-name>xep-downgrade-prevention</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Fast Authentication Streamlining Tokens</title><abstract>This specification defines a token-based method to streamline authentication in XMPP, allowing fully authenticated stream establishment within a single round-trip.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>fast</shortname><last-revision><date>2022-10-19</date><version>0.0.1</version><initials>mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-fast</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Happy Eyeballs</title><abstract>When a server's IPv4 path and protocol are working, but the server's IPv6 path and protocol are not working, a dual-stack application that initiates a connect experiences significant connection delay compared to an IPv4-only application. This is undesirable because it causes the dual-stack initiating entity to have a worse user experience. This XEP defines how IETF's 'Happy Eyeballs' algorithm requirements that reduce this user-visible delay are applied to XMPP.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2024-09-19</date><version>1.0.0</version><initials>gk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-happy-eyeballs</proto-name></xep><xep accepted="false"><number>xxxx</number><title>HTTP Online Meetings</title><abstract>This specification defines a protocol extension to request URLs from an external HTTP entity usable to initiate and invite participants to an online meeting.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>http_online-meetings</shortname><last-revision><date>2023-09-12</date><version>0.0.3</version><initials>gdk</initials><remark>* Modified wording of abstract.
* Specified distribution of URL / add meeting invitation
* Differentiate between Meeting service providers that are integrated with XMPP server, and those that are not.
* Differentiate between URL to create and join meeting
* Replaced textual references with XML entities
* Introduced distinct namespaces for create and invite, retaining type-specific namespaces for feature discovery
* Introduced Meeting Service type registry
* Removed CORS-related implementation note
* Meeting ID in request now optional
* Add optional 'desc' in the meeting request.
* Moved IQ child elements into a wrapper, renamed 'create' element to 'initiate'
* Add fall-back body element to invite message stanza.
* Removed dependency on XEP-0066.</remark></last-revision><sig>Standards</sig><proto-name>xep-http_online_meetings</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Implicit XMPP WebSocket Endpoints</title><abstract>This document specifies implicit connection endpoints for XMPP over WebSocket (RFC 7395).</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>iwe</shortname><last-revision><date>2020-01-28</date><version>0.0.1</version><initials>fs</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-iwe</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Message Displayed Synchronization</title><abstract>This specification allows multiple clients of the same user to synchronize the displayed state of their chats.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>mds</shortname><last-revision><date>2024-04-26</date><version>0.0.3</version><initials>dg</initials><remark>Split Business Rules into Server and Client sections.</remark></last-revision><sig>Standards</sig><proto-name>xep-mds</proto-name></xep><xep accepted="false"><number>xxxx</number><title>OAuth Client Login</title><abstract>This specification details how a third-party can be securely granted access to an XMPP account without exposing the account credentials, using OAuth.</abstract><type>Informational</type><status>ProtoXEP</status><approver>Council</approver><shortname>tsa</shortname><last-revision><date>2024-08-20</date><version>0.0.1</version><initials>mjw</initials><remark>
</remark></last-revision><sig>Standards</sig><proto-name>xep-oauth-client-login</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Reporting Account Affiliations</title><abstract>This specification documents a way for an XMPP server to report to other entities the relationship it has with a user on its domain.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>raa</shortname><last-revision><date>2023-06-28</date><version>0.0.1</version><initials>mjw</initials><remark>
</remark></last-revision><sig>Standards</sig><proto-name>xep-reporting-account-affiliations</proto-name></xep><xep accepted="false"><number>xxxx</number><title>SASL Channel-Binding Type Capability</title><abstract>This specification allows servers to annouce their supported SASL channel-binding types to clients.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sasl-cb-types</shortname><last-revision><date>2020-05-20</date><version>0.0.1</version><initials>fs</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-sasl-cb-types</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stanza Content Encryption</title><abstract>The Stanza Content Encryption (SCE) protocol is intended as a way to allow clients to securely exchange arbitrary extension elements using different end-to-end encryption schemes.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>SCE</shortname><last-revision><date>2019-06-03</date><version>0.0.1</version><initials>ps</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-sce</proto-name></xep><xep accepted="false"><number>xxxx</number><title>SASL Upgrade Tasks</title><abstract>This specification provides a way to upgrade to newer SASL mechanisms using SASL2 tasks.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sut</shortname><last-revision><date>2022-12-30</date><version>0.0.2</version><initials>tm</initials><remark>Move SASL upgrade tasks from XEP-0388.</remark></last-revision><sig>Standards</sig><proto-name>xep-scram-upgrade</proto-name></xep><xep accepted="false"><number>xxxx</number><title>Stream Limits Advertisement</title><abstract>This specification defines a way for an XMPP entity to announce the limits it will enforce for data received on a stream.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><shortname>sla</shortname><last-revision><date>2022-10-20</date><version>0.0.1</version><initials>ka, mw</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-sla</proto-name></xep><xep accepted="false"><number>xxxx</number><title>MUC Slow Mode</title><abstract>This specification describes a way to rate limit messages a single user can send to a MUC room. It includes room configuration option, and how servers and clients can handle such a feature.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><tags><tag>muc</tag><tag>slow mode</tag></tags><last-revision><date>2024-02-28</date><version>0.0.1</version><initials>psa</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xep-slow-mode</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP over QUIC</title><abstract>This specification defines a procedure to make both c2s and s2s XMPP connections over the QUIC protocol instead of TCP+TLS.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2022-06-13</date><version>0.0.1</version><initials>tjb</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xmpp-over-quic</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Over RELOAD (XOR)</title><abstract>This specification defines an XMPP Usage of REsource LOcation And Discovery (RELOAD). The XMPP usage provides an ability for XMPP clients to discover other peers' location through the peer-to-peer overlay. Once a peer location is determined, the RELOAD AppAttach method is used to establish a direct connection between peers through which XMPP streams are exchanged.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2019-02-08</date><version>0.0.1</version><initials>evk</initials><remark>First draft.</remark></last-revision><sig>Standards</sig><proto-name>xor</proto-name></xep><xep accepted="false"><number>xxxx</number><title>XMPP Transport Layer Security</title><abstract>This document specifies the XMPP Transport Layer Security (XTLS) protocol. XTLS, which provides communications privacy for the Extensible Messaging and Presence Protocol (XMPP), enables XMPP applications to communicate in a way that is designed to prevent eavesdropping, tampering, and forgery of XMPP stanzas. XTLS is based on Transport Layer Security (TLS) and provides equivalent security guarantees. The protocol sends standard TLS handshake and application data encoded as Base64, similar to the XMPP In-Band Bytestreams (IBB) extension but qualified by a dedicated namespace.</abstract><type>Standards Track</type><status>ProtoXEP</status><approver>Council</approver><last-revision><date>2008-12-11</date><version>0.0.5</version><initials>dm/psa</initials><remark>* By popular demand, resurrected the proposal.
* Removed IBB dependency and replaced it with a similar method in the XTLS namespace.
* Added explicit proceed and closed elements in the IQ-result stanzas.
* Removed seq attribute.
* Moved offer semantics from XEP-0250 to this specification.</remark></last-revision><sig>Standards</sig><proto-name>xtls</proto-name></xep></xep-infos>