<?xml version="1.0" ?><xeps><xep><number>0124</number><name>Bidirectional-streams Over Synchronous HTTP (BOSH)</name><type>Standards Track</type><status>Draft</status><updated>2010-07-02</updated><shortname>bosh</shortname><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></xep>
<xep><number>0045</number><name>Multi-User Chat</name><type>Standards Track</type><status>Draft</status><updated>2008-07-16</updated><shortname>muc</shortname><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></xep>
<xep><number>0001</number><name>XMPP Extension Protocols</name><type>Procedural</type><status>Active</status><updated>2010-03-10</updated><shortname>N/A</shortname><abstract>This document defines the standards process followed by the XMPP Standards Foundation.</abstract></xep>
<xep><number>0003</number><name>Proxy Accept Socket Service (PASS)</name><type>Historical</type><status>Obsolete</status><updated>2009-06-03</updated><shortname>pass</shortname><abstract>This document defines a method for relaying media via proxies on the Jabber/XMPP network.</abstract></xep>
<xep><number>0004</number><name>Data Forms</name><type>Standards Track</type><status>Final</status><updated>2007-08-13</updated><shortname>x-data</shortname><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></xep>
<xep><number>0008</number><name>IQ-Based Avatars</name><type>Historical</type><status>Deferred</status><updated>2005-06-16</updated><shortname>None</shortname><abstract>This specification provides historical documentation of an IQ-based protocol for exchanging user avatars.</abstract></xep>
<xep><number>0009</number><name>Jabber-RPC</name><type>Standards Track</type><status>Final</status><updated>2011-11-10</updated><shortname>jabber-rpc</shortname><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></xep>
<xep><number>0011</number><name>Jabber Browsing</name><type>Historical</type><status>Obsolete</status><updated>2009-06-03</updated><shortname>iq-browse</shortname><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></xep>
<xep><number>0012</number><name>Last Activity</name><type>Standards Track</type><status>Final</status><updated>2008-11-26</updated><shortname>iq-last</shortname><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></xep>
<xep><number>0013</number><name>Flexible Offline Message Retrieval</name><type>Standards Track</type><status>Draft</status><updated>2005-07-14</updated><shortname>offline</shortname><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></xep>
<xep><number>0016</number><name>Privacy Lists</name><type>Standards Track</type><status>Draft</status><updated>2007-02-15</updated><shortname>privacy</shortname><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></xep>
<xep><number>0018</number><name>Invisible Presence</name><type>Informational</type><status>Rejected</status><updated>2003-09-26</updated><shortname>N/A</shortname><abstract>Documentation of invisible presence.</abstract></xep>
<xep><number>0020</number><name>Feature Negotiation</name><type>Standards Track</type><status>Draft</status><updated>2006-11-21</updated><shortname>feature-neg</shortname><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></xep>
<xep><number>0021</number><name>Jabber Event Notification Service (ENS)</name><type>Standards Track</type><status>Retracted</status><updated>2003-04-22</updated><shortname>None</shortname><abstract>A generic publish-and-subscribe service for Jabber.</abstract></xep>
<xep><number>0022</number><name>Message Events</name><type>Historical</type><status>Obsolete</status><updated>2009-05-27</updated><shortname>x-event</shortname><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></xep>
<xep><number>0023</number><name>Message Expiration</name><type>Historical</type><status>Obsolete</status><updated>2009-06-03</updated><shortname>x-expire</shortname><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></xep>
<xep><number>0024</number><name>Publish/Subscribe</name><type>Standards Track</type><status>Retracted</status><updated>2003-04-22</updated><shortname>None</shortname><abstract>A publish-subscribe protocol for Jabber.</abstract></xep>
<xep><number>0025</number><name>Jabber HTTP Polling</name><type>Historical</type><status>Obsolete</status><updated>2009-06-03</updated><shortname>httppoll</shortname><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></xep>
<xep><number>0026</number><name>Internationalization (I18N)</name><type>Standards Track</type><status>Retracted</status><updated>2003-11-05</updated><shortname>N/A</shortname><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></xep>
<xep><number>0027</number><name>Current Jabber OpenPGP Usage</name><type>Historical</type><status>Active</status><updated>2006-11-29</updated><shortname>openpgp</shortname><abstract>This document outlines the current usage of OpenPGP for messaging and presence.</abstract></xep>
<xep><number>0028</number><name>No Such XEP</name><type>Informational</type><status>Retracted</status><updated>2001-08-20</updated><shortname>N/A</shortname><abstract>This document was removed from the XSF website and source control at the request of the author.</abstract></xep>
<xep><number>0029</number><name>Definition of Jabber Identifiers (JIDs)</name><type>Standards Track</type><status>Retracted</status><updated>2003-10-03</updated><shortname>N/A</shortname><abstract>This document defines the exact nature of a Jabber Identifier (JID). </abstract></xep>
<xep><number>0030</number><name>Service Discovery</name><type>Standards Track</type><status>Final</status><updated>2008-06-06</updated><shortname>disco</shortname><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></xep>
<xep><number>0033</number><name>Extended Stanza Addressing</name><type>Standards Track</type><status>Draft</status><updated>2004-09-15</updated><shortname>address</shortname><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></xep>
<xep><number>0034</number><name>SASL Integration</name><type>Standards Track</type><status>Retracted</status><updated>2003-11-05</updated><shortname>N/A</shortname><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></xep>
<xep><number>0035</number><name>SSL/TLS Integration</name><type>Standards Track</type><status>Retracted</status><updated>2003-11-05</updated><shortname>N/A</shortname><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></xep>
<xep><number>0036</number><name>Pub-Sub Subscriptions</name><type>Standards Track</type><status>Retracted</status><updated>2003-04-22</updated><shortname>None</shortname><abstract>A proposal for the subscribe half of a publish-subscribe protocol within Jabber.</abstract></xep>
<xep><number>0038</number><name>Icon Styles</name><type>Standards Track</type><status>Deferred</status><updated>2003-06-02</updated><shortname>None</shortname><abstract>A protocol for specifying exchangeable styles of emoticons and genicons within Jabber IM clients.</abstract></xep>
<xep><number>0040</number><name>Jabber Robust Publish-Subscribe</name><type>Standards Track</type><status>Retracted</status><updated>2004-07-26</updated><shortname>None</shortname><abstract>Note: This proposal has been superseded by XEP-0060; please refer to that document for the successor protocol.</abstract></xep>
<xep><number>0041</number><name>Reliable Entity Link</name><type>Standards Track</type><status>Retracted</status><updated>2003-09-30</updated><shortname>rel</shortname><abstract>Protocol for linking a bytestream between two Jabber entities.</abstract></xep>
<xep><number>0042</number><name>Jabber OOB Broadcast Service (JOBS)</name><type>Standards Track</type><status>Retracted</status><updated>2003-04-11</updated><shortname>JOBS</shortname><abstract>A protocol for enabling uni-directional multicast data transfers out of band.</abstract></xep>
<xep><number>0046</number><name>DTCP</name><type>Standards Track</type><status>Retracted</status><updated>2003-04-11</updated><shortname>None</shortname><abstract>Direct TCP connection between two Jabber entities.</abstract></xep>
<xep><number>0047</number><name>In-Band Bytestreams</name><type>Standards Track</type><status>Draft</status><updated>2011-03-01</updated><shortname>ibb</shortname><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></xep>
<xep><number>0048</number><name>Bookmarks</name><type>Standards Track</type><status>Draft</status><updated>2007-11-07</updated><shortname>bookmarks</shortname><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></xep>
<xep><number>0049</number><name>Private XML Storage</name><type>Historical</type><status>Active</status><updated>2004-03-01</updated><shortname>iq-private</shortname><abstract>This specification provides canonical documentation of the 'jabber:iq:private' namespace currently in common usage.</abstract></xep>
<xep><number>0050</number><name>Ad-Hoc Commands</name><type>Standards Track</type><status>Draft</status><updated>2005-06-30</updated><shortname>commands</shortname><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></xep>
<xep><number>0052</number><name>File Transfer</name><type>Standards Track</type><status>Retracted</status><updated>2003-09-30</updated><shortname>N/A</shortname><abstract>A protocol for transferring a file between two Jabber IDs.</abstract></xep>
<xep><number>0053</number><name>XMPP Registrar Function</name><type>Procedural</type><status>Active</status><updated>2008-10-29</updated><shortname>N/A</shortname><abstract>This document defines the roles and processes of the XMPP Registrar function within the XMPP Standards Foundation.</abstract></xep>
<xep><number>0054</number><name>vcard-temp</name><type>Historical</type><status>Active</status><updated>2008-07-16</updated><shortname>vcard-temp</shortname><abstract>This specification provides canonical documentation of the vCard-XML format currently in use within the Jabber community.</abstract></xep>
<xep><number>0055</number><name>Jabber Search</name><type>Historical</type><status>Active</status><updated>2009-09-15</updated><shortname>iq-search</shortname><abstract>This specification provides canonical documentation of the jabber:iq:search namespace currently in use within the Jabber community.</abstract></xep>
<xep><number>0057</number><name>Extended Roster</name><type>Standards Track</type><status>Retracted</status><updated>2003-04-28</updated><shortname>None</shortname><abstract>This document defines a way to handle extended roster items.</abstract></xep>
<xep><number>0059</number><name>Result Set Management</name><type>Standards Track</type><status>Draft</status><updated>2006-09-20</updated><shortname>rsm</shortname><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></xep>
<xep><number>0060</number><name>Publish-Subscribe</name><type>Standards Track</type><status>Draft</status><updated>2010-07-12</updated><shortname>pubsub</shortname><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></xep>
<xep><number>0061</number><name>Shared Notes</name><type>Informational</type><status>Deferred</status><updated>2003-09-30</updated><shortname>Not yet assigned</shortname><abstract>A simplistic mechanism for shared notes, modeled after common stickie note applications.</abstract></xep>
<xep><number>0062</number><name>Packet Filtering</name><type>Informational</type><status>Deferred</status><updated>2003-09-30</updated><shortname>Not yet assigned</shortname><abstract>A framework for packet filtering rules.</abstract></xep>
<xep><number>0063</number><name>Basic Filtering Operations</name><type>Informational</type><status>Deferred</status><updated>2003-09-30</updated><shortname>Not yet assigned</shortname><abstract>A module that provides basic conditions and actions for packet filtering.</abstract></xep>
<xep><number>0064</number><name>XPath Filtering</name><type>Informational</type><status>Deferred</status><updated>2003-09-30</updated><shortname>Not yet assigned</shortname><abstract>A module that provides an XPath matching condition for packet filtering.</abstract></xep>
<xep><number>0065</number><name>SOCKS5 Bytestreams</name><type>Standards Track</type><status>Draft</status><updated>2011-04-20</updated><shortname>bytestreams</shortname><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></xep>
<xep><number>0066</number><name>Out of Band Data</name><type>Standards Track</type><status>Draft</status><updated>2006-08-16</updated><shortname>oob</shortname><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></xep>
<xep><number>0068</number><name>Field Standardization for Data Forms</name><type>Informational</type><status>Active</status><updated>2011-10-18</updated><shortname>formtypes</shortname><abstract>This document specifies how to standardize field variables used in the context of jabber:x:data forms.</abstract></xep>
<xep><number>0070</number><name>Verifying HTTP Requests via XMPP</name><type>Standards Track</type><status>Draft</status><updated>2005-12-14</updated><shortname>http-auth</shortname><abstract>This specification defines an XMPP protocol extension that enables verification of an HTTP request via XMPP.</abstract></xep>
<xep><number>0071</number><name>XHTML-IM</name><type>Standards Track</type><status>Draft</status><updated>2008-09-03</updated><shortname>xhtml-im</shortname><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></xep>
<xep><number>0072</number><name>SOAP Over XMPP</name><type>Standards Track</type><status>Draft</status><updated>2005-12-14</updated><shortname>soap</shortname><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></xep>
<xep><number>0073</number><name>Basic IM Protocol Suite</name><type>Standards Track</type><status>Obsolete</status><updated>2007-10-30</updated><shortname>N/A</shortname><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></xep>
<xep><number>0074</number><name>Simple Access Control</name><type>Standards Track</type><status>Retracted</status><updated>2003-10-20</updated><shortname>sac</shortname><abstract>A simple protocol for querying information for permissions.</abstract></xep>
<xep><number>0075</number><name>Jabber Object Access Protocol (JOAP)</name><type>Standards Track</type><status>Deferred</status><updated>2003-05-22</updated><shortname>N/A</shortname><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></xep>
<xep><number>0076</number><name>Malicious Stanzas</name><type>Humorous</type><status>Active</status><updated>2003-04-01</updated><shortname>evil</shortname><abstract>This document defines an XMPP protocol extension for flagging malicious stanzas.</abstract></xep>
<xep><number>0077</number><name>In-Band Registration</name><type>Standards Track</type><status>Final</status><updated>2012-01-25</updated><shortname>iq-register</shortname><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></xep>
<xep><number>0078</number><name>Non-SASL Authentication</name><type>Standards Track</type><status>Obsolete</status><updated>2008-10-29</updated><shortname>iq-auth</shortname><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></xep>
<xep><number>0079</number><name>Advanced Message Processing</name><type>Standards Track</type><status>Draft</status><updated>2005-11-30</updated><shortname>amp</shortname><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></xep>
<xep><number>0080</number><name>User Location</name><type>Standards Track</type><status>Draft</status><updated>2009-09-15</updated><shortname>geoloc</shortname><abstract>This specification defines an XMPP protocol extension for communicating information about the current geographical or physical location of an entity.</abstract></xep>
<xep><number>0081</number><name>Jabber MIME Type</name><type>Standards Track</type><status>Retracted</status><updated>2005-07-19</updated><shortname>mimetype</shortname><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></xep>
<xep><number>0082</number><name>XMPP Date and Time Profiles</name><type>Informational</type><status>Active</status><updated>2003-05-28</updated><shortname>N/A</shortname><abstract>This document specifies a standardization of ISO 8601 profiles and their lexical representation for use in XMPP protocol extensions.</abstract></xep>
<xep><number>0083</number><name>Nested Roster Groups</name><type>Informational</type><status>Active</status><updated>2004-10-11</updated><shortname>nestedgroups</shortname><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></xep>
<xep><number>0084</number><name>User Avatar</name><type>Standards Track</type><status>Draft</status><updated>2008-11-05</updated><shortname>avatar</shortname><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></xep>
<xep><number>0085</number><name>Chat State Notifications</name><type>Standards Track</type><status>Final</status><updated>2009-09-23</updated><shortname>chatstates</shortname><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></xep>
<xep><number>0002</number><name>Special Interest Groups (SIGs)</name><type>Procedural</type><status>Active</status><updated>2002-01-11</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A definition of Special Interest Groups within the XMPP Standards Foundation.</abstract></xep>
<xep><number>0005</number><name>Jabber Interest Groups</name><type>Informational</type><status>Obsolete</status><updated>2002-05-08</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This is the official list and summary information of the Jabber Interest Groups.</abstract></xep>
<xep><number>0006</number><name>Profiles</name><type>SIG Formation</type><status>Obsolete</status><updated>2002-05-08</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal for a more powerful and extensible protocol for the management of personal information within Jabber.</abstract></xep>
<xep><number>0007</number><name>Conferencing SIG</name><type>SIG Proposal</type><status>Obsolete</status><updated>2002-05-08</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal for a Jabber Interest Group that will discuss the protocol for implementing many-to-many communications.</abstract></xep>
<xep><number>0010</number><name>Whiteboarding SIG</name><type>SIG Formation</type><status>Obsolete</status><updated>2002-05-08</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal to form a SIG to develop a protocol for whiteboarding over Jabber.</abstract></xep>
<xep><number>0014</number><name>Message Tone</name><type>Standards Track</type><status>Rejected</status><updated>2002-01-16</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal for including the sender's tone in messages.</abstract></xep>
<xep><number>0015</number><name>Account Transfer</name><type>Standards Track</type><status>Rejected</status><updated>2002-04-18</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal for enabling the ability to transfer an account from one Jabber server to another.</abstract></xep>
<xep><number>0017</number><name>Naive Packet Framing Protocol</name><type>Informational</type><status>Rejected</status><updated>2002-02-19</updated><shortname>NOT YET ASSIGNED</shortname><abstract>An intermediate method for more efficient framing of the Jabber XML Stream.</abstract></xep>
<xep><number>0019</number><name>Streamlining the SIGs</name><type>Procedural</type><status>Active</status><updated>2002-03-20</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This document proposes to streamline the existing Special Interest Groups (SIGs).</abstract></xep>
<xep><number>0031</number><name>A Framework For Securing Jabber Conversations</name><type>Standards Track</type><status>Deferred</status><updated>2002-07-09</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0032</number><name>Jabber URI Scheme</name><type>Standards Track</type><status>Retracted</status><updated>2003-09-02</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A URI scheme for Jabber communications.</abstract></xep>
<xep><number>0037</number><name>DSPS - Data Stream Proxy Service</name><type>Standards Track</type><status>Rejected</status><updated>2002-09-18</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal for proxy support in Jabber.</abstract></xep>
<xep><number>0039</number><name>Statistics Gathering</name><type>Standards Track</type><status>Deferred</status><updated>2002-11-05</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A protocol to enable gathering statistics from Jabber servers and components.</abstract></xep>
<xep><number>0043</number><name>Jabber Database Access</name><type>Standards Track</type><status>Retracted</status><updated>2003-10-20</updated><shortname>NOT YET ASSIGNED</shortname><abstract>Expose RDBM systems directly to the jabber network</abstract></xep>
<xep><number>0044</number><name>Full Namespace Support for XML Streams</name><type>Standards Track</type><status>Deferred</status><updated>2002-08-26</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A description of the use of namespaces within Jabber.</abstract></xep>
<xep><number>0051</number><name>Connection Transfer</name><type>Standards Track</type><status>Deferred</status><updated>2009-07-07</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0056</number><name>Business Data Interchange</name><type>Standards Track</type><status>Deferred</status><updated>2002-11-18</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This document defines a way to transmit ebXML messages, ANSI X.11, EDIFACT/UN, and SAP iDoc over Jabber/XMPP.</abstract></xep>
<xep><number>0058</number><name>Multi-User Text Editing</name><type>Standards Track</type><status>Deferred</status><updated>2002-11-12</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This document defines how several people may simultaneously edit text.</abstract></xep>
<xep><number>0067</number><name>Stock Data Transmission</name><type>Standards Track</type><status>Deferred</status><updated>2003-07-19</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This document specifies a data format for stock data distribution in the Jabber community.</abstract></xep>
<xep><number>0069</number><name>Compliance SIG</name><type>SIG Formation</type><status>Deferred</status><updated>2003-01-29</updated><shortname>NOT YET ASSIGNED</shortname><abstract>A proposal to form a SIG devoted to issues related to protocol compliance.</abstract></xep>
<xep><number>0086</number><name>Error Condition Mappings</name><type>Informational</type><status>Deprecated</status><updated>2004-02-17</updated><shortname>N/A</shortname><abstract>A mapping to enable legacy entities to correctly handle errors from XMPP-aware entities.</abstract></xep>
<xep><number>0087</number><name>Stream Initiation</name><type>Standards Track</type><status>Retracted</status><updated>2003-05-22</updated><shortname>si</shortname><abstract>A common method to initiate a stream with meta information</abstract></xep>
<xep><number>0088</number><name>Client Webtabs</name><type>Informational</type><status>Deferred</status><updated>2004-03-14</updated><shortname>webtab</shortname><abstract>A protocol for displaying web-based tabs in clients.</abstract></xep>
<xep><number>0089</number><name>Generic Alerts</name><type>Standards Track</type><status>Deferred</status><updated>2003-05-16</updated><shortname>Not yet assigned</shortname><abstract>A protocol for generic alerts (similar to .NET Alerts service).</abstract></xep>
<xep><number>0090</number><name>Legacy Entity Time</name><type>Historical</type><status>Obsolete</status><updated>2009-05-27</updated><shortname>iq-time</shortname><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></xep>
<xep><number>0091</number><name>Legacy Delayed Delivery</name><type>Historical</type><status>Obsolete</status><updated>2009-05-27</updated><shortname>x-delay</shortname><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></xep>
<xep><number>0092</number><name>Software Version</name><type>Standards Track</type><status>Draft</status><updated>2007-02-15</updated><shortname>iq-version</shortname><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></xep>
<xep><number>0093</number><name>Roster Item Exchange</name><type>Historical</type><status>Deprecated</status><updated>2005-08-26</updated><shortname>x-roster</shortname><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></xep>
<xep><number>0094</number><name>Agent Information</name><type>Historical</type><status>Obsolete</status><updated>2003-10-08</updated><shortname>iq-agents</shortname><abstract>This specification provides canonical documentation of the obsolete Agent Information namespace. Note: This document has been superseded by XEP-0030: Service Discovery.</abstract></xep>
<xep><number>0095</number><name>Stream Initiation</name><type>Standards Track</type><status>Draft</status><updated>2004-04-13</updated><shortname>si</shortname><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></xep>
<xep><number>0096</number><name>SI File Transfer</name><type>Standards Track</type><status>Draft</status><updated>2004-04-13</updated><shortname>si-filetransfer</shortname><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></xep>
<xep><number>0097</number><name>iCal Envelope</name><type>Standards Track</type><status>Deferred</status><updated>2003-06-10</updated><shortname>ice</shortname><abstract>A simple mechanism to transport iCal data over the jabber protocol</abstract></xep>
<xep><number>0098</number><name>Enhanced Private XML Storage</name><type>Standards Track</type><status>Deferred</status><updated>2003-06-25</updated><shortname>private-xml</shortname><abstract>Standardizes &quot;private&quot; XML data storage.</abstract></xep>
<xep><number>0099</number><name>IQ Query Action Protocol</name><type>Standards Track</type><status>Deferred</status><updated>2003-06-25</updated><shortname>Not yet assigned</shortname><abstract>Standardizes behavior of   actions for generic query behavior.</abstract></xep>
<xep><number>0100</number><name>Gateway Interaction</name><type>Informational</type><status>Active</status><updated>2005-10-05</updated><shortname>gateway</shortname><abstract>This document specifies best practices for interactions between Jabber clients and client proxy gateways to legacy IM services.</abstract></xep>
<xep><number>0101</number><name>HTTP Authentication using Jabber Tickets</name><type>Standards Track</type><status>Deferred</status><updated>2004-01-18</updated><shortname>Not yet assigned</shortname><abstract>This document defines a protocol for authenticating HTTP requests using Jabber Tickets.</abstract></xep>
<xep><number>0102</number><name>Security Extensions</name><type>Standards Track</type><status>Deferred</status><updated>2003-06-25</updated><shortname>Not yet assigned</shortname><abstract>Security extensions for Jabber/XMPP.</abstract></xep>
<xep><number>0103</number><name>URL Address Information</name><type>Standards Track</type><status>Deferred</status><updated>2004-01-20</updated><shortname>url-data</shortname><abstract>This document defines a structure for providing information about an Uniform Resource Locator (URL), and a protocol signaling retrieval states.</abstract></xep>
<xep><number>0104</number><name>HTTP Scheme for URL Data</name><type>Standards Track</type><status>Deferred</status><updated>2004-01-20</updated><shortname>N/A</shortname><abstract>This document provides a schema description for detailed information about HTTP URLs.</abstract></xep>
<xep><number>0105</number><name>Tree Transfer Stream Initiation Profile</name><type>Standards Track</type><status>Deferred</status><updated>2003-09-22</updated><shortname>si-treetransfer</shortname><abstract>A profile describing meta-data for transferring trees of files using stream inititation.</abstract></xep>
<xep><number>0106</number><name>JID Escaping</name><type>Standards Track</type><status>Draft</status><updated>2007-06-18</updated><shortname>jid\20escaping</shortname><abstract>This specification defines a mechanism that enables the display in Jabber Identifiers (JIDs) of characters disallowed by the Nodeprep profile of stringprep. Although these characters -- space, double quote, ampersand, single quote, forward slash, colon, less than, greater than, and at-sign -- cannot be included in XMPP node identifiers, 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></xep>
<xep><number>0107</number><name>User Mood</name><type>Standards Track</type><status>Draft</status><updated>2008-10-29</updated><shortname>mood</shortname><abstract>This specification defines a payload format for communicating information about user moods, such as whether a person is currently happy, sad, angy, or annoyed. The payload format is typically transported using the personal eventing protocol, a profile of XMPP publish-subscribe specified in XEP-0163.</abstract></xep>
<xep><number>0108</number><name>User Activity</name><type>Standards Track</type><status>Draft</status><updated>2008-10-29</updated><shortname>activity</shortname><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></xep>
<xep><number>0109</number><name>Out-of-Office Messages</name><type>Standards Track</type><status>Deferred</status><updated>2010-05-24</updated><shortname>ooo</shortname><abstract>This document defines an XMPP protocol extension for communicating out-of-office status.</abstract></xep>
<xep><number>0110</number><name>Generic Maps</name><type>Standards Track</type><status>Deferred</status><updated>2003-07-28</updated><shortname>Not yet assigned</shortname><abstract>A protocol for transport of generic maps (graphical displays of specific subsets of buddies).</abstract></xep>
<xep><number>0111</number><name>A Transport for Initiating and Negotiating Sessions (TINS)</name><type>Standards Track</type><status>Retracted</status><updated>2005-12-21</updated><shortname>tins</shortname><abstract>This document defined a SIP-compatible transport for initiating and negotiating sessions using SDP over XMPP.</abstract></xep>
<xep><number>0112</number><name>User Physical Location</name><type>Standards Track</type><status>Obsolete</status><updated>2004-10-12</updated><shortname>physloc</shortname><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></xep>
<xep><number>0113</number><name>Simple Whiteboarding</name><type>Informational</type><status>Deferred</status><updated>2003-09-07</updated><shortname>Not yet assigned</shortname><abstract>A proposal for an extremely simple whiteboarding protocol over Jabber.</abstract></xep>
<xep><number>0114</number><name>Jabber Component Protocol</name><type>Historical</type><status>Active</status><updated>2012-01-25</updated><shortname>component</shortname><abstract>This specification documents the existing protocol used for communication between servers and &quot;external&quot; components over the Jabber network.</abstract></xep>
<xep><number>0115</number><name>Entity Capabilities</name><type>Standards Track</type><status>Draft</status><updated>2008-02-26</updated><shortname>caps</shortname><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></xep>
<xep><number>0116</number><name>Encrypted Session Negotiation</name><type>Standards Track</type><status>Deferred</status><updated>2007-05-30</updated><shortname>TO BE ASSIGNED</shortname><abstract>This document specifies an XMPP protocol extension for negotiating an end-to-end encrypted session.</abstract></xep>
<xep><number>0117</number><name>Intermediate IM Protocol Suite</name><type>Standards Track</type><status>Obsolete</status><updated>2007-10-30</updated><shortname>N/A</shortname><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></xep>
<xep><number>0118</number><name>User Tune</name><type>Standards Track</type><status>Draft</status><updated>2008-01-30</updated><shortname>tune</shortname><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></xep>
<xep><number>0119</number><name>Extended Presence Protocol Suite</name><type>Standards Track</type><status>Retracted</status><updated>2006-08-08</updated><shortname>N/A</shortname><abstract>This document specifies a set of XMPP extensions that provide support for extended presence information. Note: This document has been retracted since its functionality is handled by XEP-0163.</abstract></xep>
<xep><number>0120</number><name>Infobits</name><type>Standards Track</type><status>Retracted</status><updated>2004-01-22</updated><shortname>infobits</shortname><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract></xep>
<xep><number>0121</number><name>Dublin Core Infobits Mapping</name><type>Informational</type><status>Retracted</status><updated>2003-12-15</updated><shortname>N/A</shortname><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract></xep>
<xep><number>0122</number><name>Data Forms Validation</name><type>Standards Track</type><status>Draft</status><updated>2004-09-22</updated><shortname>xdata-validate</shortname><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></xep>
<xep><number>0123</number><name>Entity Metadata</name><type>Standards Track</type><status>Retracted</status><updated>2003-12-16</updated><shortname>N/A</shortname><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract></xep>
<xep><number>0125</number><name>vCard Infobits Mapping</name><type>Informational</type><status>Retracted</status><updated>2003-12-15</updated><shortname>N/A</shortname><abstract>NOTE: This proposal was retracted by the author on 2004-02-19.</abstract></xep>
<xep><number>0126</number><name>Invisibility</name><type>Informational</type><status>Active</status><updated>2005-08-19</updated><shortname>N/A</shortname><abstract>This specification defines best practices regarding implementation of invisible presence by means of XMPP privacy lists.</abstract></xep>
<xep><number>0127</number><name>Common Alerting Protocol (CAP) Over XMPP</name><type>Informational</type><status>Active</status><updated>2004-12-09</updated><shortname>None</shortname><abstract>This document specifies a method for sending Common Alerting Protocol (CAP) data over XMPP.</abstract></xep>
<xep><number>0128</number><name>Service Discovery Extensions</name><type>Informational</type><status>Active</status><updated>2004-10-20</updated><shortname>N/A</shortname><abstract>This document specifies best practices for including extended information in Service Discovery results.</abstract></xep>
<xep><number>0129</number><name>WebDAV File Transfers</name><type>Standards Track</type><status>Deferred</status><updated>2007-04-19</updated><shortname>TO BE ASSIGNED</shortname><abstract>This document specifies a method for completing file transfers between XMPP entities using WebDAV.</abstract></xep>
<xep><number>0130</number><name>Waiting Lists</name><type>Historical</type><status>Active</status><updated>2006-09-13</updated><shortname>waitinglist</shortname><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></xep>
<xep><number>0131</number><name>Stanza Headers and Internet Metadata</name><type>Standards Track</type><status>Draft</status><updated>2006-07-12</updated><shortname>shim</shortname><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></xep>
<xep><number>0132</number><name>Presence Obtained via Kinesthetic Excitation (POKE)</name><type>Humorous</type><status>Active</status><updated>2004-04-01</updated><shortname>poke</shortname><abstract>This document defines an XMPP protocol extension that enables probing for presence via physical rather than electronic means.</abstract></xep>
<xep><number>0133</number><name>Service Administration</name><type>Informational</type><status>Active</status><updated>2005-08-19</updated><shortname>admin</shortname><abstract>This document defines recommended best practices for service-level administration of servers and components using Ad-Hoc Commands.</abstract></xep>
<xep><number>0134</number><name>XMPP Design Guidelines</name><type>Informational</type><status>Active</status><updated>2004-12-09</updated><shortname>N/A</shortname><abstract>This document defines best practices for the intelligent design of Jabber protocols and other XMPP extensions.</abstract></xep>
<xep><number>0135</number><name>File Sharing</name><type>Standards Track</type><status>Deferred</status><updated>2004-06-04</updated><shortname>files</shortname><abstract>This document specifies a simple extension to existing protocols for file sharing over Jabber/XMPP.</abstract></xep>
<xep><number>0136</number><name>Message Archiving</name><type>Standards Track</type><status>Draft</status><updated>2010-06-21</updated><shortname>archive</shortname><abstract>This document defines mechanisms and preferences for the server-side archiving and retrieval of XMPP messages.</abstract></xep>
<xep><number>0137</number><name>Publishing Stream Initiation Requests</name><type>Standards Track</type><status>Draft</status><updated>2005-08-26</updated><shortname>sipub</shortname><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></xep>
<xep><number>0138</number><name>Stream Compression</name><type>Standards Track</type><status>Final</status><updated>2009-05-27</updated><shortname>compress</shortname><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></xep>
<xep><number>0139</number><name>Security SIG</name><type>SIG Formation</type><status>Retracted</status><updated>2004-09-15</updated><shortname>N/A</shortname><abstract>This document proposes the formation of a Special Interest Group devoted to the analysis of security threats related to Jabber technologies.</abstract></xep>
<xep><number>0140</number><name>Shared Groups</name><type>Informational</type><status>Retracted</status><updated>2004-10-27</updated><shortname>groups</shortname><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></xep>
<xep><number>0141</number><name>Data Forms Layout</name><type>Standards Track</type><status>Draft</status><updated>2005-05-12</updated><shortname>xdata-layout</shortname><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></xep>
<xep><number>0142</number><name>Workgroup Queues</name><type>Standards Track</type><status>Deferred</status><updated>2005-05-09</updated><shortname>Not yet assigned</shortname><abstract>This document defines an XMPP protocol extension that enables a user to communicate with a representative of an organization, department, or workgroup.</abstract></xep>
<xep><number>0143</number><name>Guidelines for Authors of XMPP Extension Protocols</name><type>Procedural</type><status>Active</status><updated>2011-07-08</updated><shortname>N/A</shortname><abstract>This document provides information intended to assist authors of XMPP Extension Protocols.</abstract></xep>
<xep><number>0144</number><name>Roster Item Exchange</name><type>Standards Track</type><status>Draft</status><updated>2005-08-26</updated><shortname>rosterx</shortname><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></xep>
<xep><number>0145</number><name>Annotations</name><type>Historical</type><status>Active</status><updated>2006-03-23</updated><shortname>rosternotes</shortname><abstract>This document defines a protocol for making annotations about roster items and other entities.</abstract></xep>
<xep><number>0146</number><name>Remote Controlling Clients</name><type>Informational</type><status>Active</status><updated>2006-03-23</updated><shortname>rc</shortname><abstract>This document specifies recommended best practices for remote controlling clients using Ad-Hoc Commands.</abstract></xep>
<xep><number>0147</number><name>XMPP URI Scheme Query Components</name><type>Informational</type><status>Active</status><updated>2006-09-13</updated><shortname>querytypes</shortname><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></xep>
<xep><number>0148</number><name>Instant Messaging Intelligence Quotient (IM IQ)</name><type>Humorous</type><status>Active</status><updated>2005-04-01</updated><shortname>iq-iq</shortname><abstract>This specification provides canonical documentation of the jabber:iq:iq namespace.</abstract></xep>
<xep><number>0149</number><name>Time Periods</name><type>Informational</type><status>Active</status><updated>2006-01-24</updated><shortname>N/A</shortname><abstract>This document defines a method to specify the valid time periods for states, events, and activities communicated via Jabber/XMPP protocols.</abstract></xep>
<xep><number>0150</number><name>Use of Entity Tags in XMPP Extensions</name><type>Informational</type><status>Deferred</status><updated>2005-08-09</updated><shortname>N/A</shortname><abstract>This document defines best practices for the use of Entity Tags in XMPP extensions.</abstract></xep>
<xep><number>0151</number><name>Virtual Presence</name><type>Standards Track</type><status>Deferred</status><updated>2005-07-05</updated><shortname>Not yet assigned</shortname><abstract>This document proposes extensions to the Jabber groupchat protocol for virtual presence on Web pages.</abstract></xep>
<xep><number>0152</number><name>Reachability Addresses</name><type>Standards Track</type><status>Deferred</status><updated>2008-10-06</updated><shortname>reach</shortname><abstract>This document defines an XMPP protocol extension for communicating reachability information related to non-XMPP devices.</abstract></xep>
<xep><number>0153</number><name>vCard-Based Avatars</name><type>Historical</type><status>Active</status><updated>2006-08-16</updated><shortname>vcard-avatar</shortname><abstract>This document provides historical documentation of a vCard-based protocol for exchanging user avatars.</abstract></xep>
<xep><number>0154</number><name>User Profile</name><type>Standards Track</type><status>Deferred</status><updated>2008-04-18</updated><shortname>TO-BE-ASSIGNED</shortname><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></xep>
<xep><number>0155</number><name>Stanza Session Negotiation</name><type>Standards Track</type><status>Draft</status><updated>2008-01-14</updated><shortname>ssn</shortname><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></xep>
<xep><number>0156</number><name>Discovering Alternative XMPP Connection Methods</name><type>Standards Track</type><status>Draft</status><updated>2007-06-12</updated><shortname>alt-connections</shortname><abstract>This document defines a DNS TXT Resource Record format for use in discovering alternative methods of connecting to an XMPP server.</abstract></xep>
<xep><number>0157</number><name>Contact Addresses for XMPP Services</name><type>Informational</type><status>Active</status><updated>2007-01-31</updated><shortname>N/A</shortname><abstract>This document defines a method for specifying contact addresses related to an XMPP service.</abstract></xep>
<xep><number>0158</number><name>CAPTCHA Forms</name><type>Standards Track</type><status>Draft</status><updated>2008-09-03</updated><shortname>captcha</shortname><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></xep>
<xep><number>0159</number><name>Spim-Blocking Control</name><type>Standards Track</type><status>Deferred</status><updated>2006-07-11</updated><shortname>TO BE ASSIGNED</shortname><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></xep>
<xep><number>0160</number><name>Best Practices for Handling Offline Messages</name><type>Informational</type><status>Active</status><updated>2006-01-24</updated><shortname>msgoffline</shortname><abstract>This document specifies best practices to be followed by Jabber/XMPP servers in handling messages sent to recipients who are offline.</abstract></xep>
<xep><number>0161</number><name>Abuse Reporting</name><type>Standards Track</type><status>Deferred</status><updated>2007-05-06</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document specifies an XMPP protocol extension for reporting abusive XMPP stanzas. NOTE: This specification has been superseded by XEP-0268.</abstract></xep>
<xep><number>0162</number><name>Best Practices for Roster and Subscription Management</name><type>Informational</type><status>Deferred</status><updated>2005-12-06</updated><shortname>N/A</shortname><abstract>This document specifies best practices for roster and subscription management in Jabber/XMPP clients.</abstract></xep>
<xep><number>0163</number><name>Personal Eventing Protocol</name><type>Standards Track</type><status>Draft</status><updated>2010-07-12</updated><shortname>pep</shortname><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></xep>
<xep><number>0164</number><name>vCard Filtering</name><type>Standards Track</type><status>Deferred</status><updated>2005-11-16</updated><shortname>vcard-temp-filter</shortname><abstract>This document specifies a mechanism for requesting specific sections of a vCard.</abstract></xep>
<xep><number>0165</number><name>Best Practices to Discourage JID Mimicking</name><type>Informational</type><status>Deferred</status><updated>2007-12-13</updated><shortname>N/A</shortname><abstract>This document recommends best practices to discourage mimicking of Jabber IDs.</abstract></xep>
<xep><number>0166</number><name>Jingle</name><type>Standards Track</type><status>Draft</status><updated>2009-12-23</updated><shortname>jingle</shortname><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></xep>
<xep><number>0167</number><name>Jingle RTP Sessions</name><type>Standards Track</type><status>Draft</status><updated>2009-12-23</updated><shortname>jingle-rtp</shortname><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></xep>
<xep><number>0168</number><name>Resource Application Priority</name><type>Standards Track</type><status>Deferred</status><updated>2008-09-26</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document defines an XMPP protocol extension to indicate the presence priority of XMPP resources for applications other than standard XMPP messaging.</abstract></xep>
<xep><number>0169</number><name>Twas The Night Before Christmas (Jabber Version)</name><type>Humorous</type><status>Active</status><updated>2009-12-24</updated><shortname>N/A</shortname><abstract>The classic Christmas poem annotated with XMPP protocols.</abstract></xep>
<xep><number>0170</number><name>Recommended Order of Stream Feature Negotiation</name><type>Informational</type><status>Active</status><updated>2007-01-04</updated><shortname>N/A</shortname><abstract>This document specifies a recommended order for negotiation of XMPP stream features.</abstract></xep>
<xep><number>0171</number><name>Language Translation</name><type>Standards Track</type><status>Draft</status><updated>2011-06-15</updated><shortname>langtrans</shortname><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></xep>
<xep><number>0172</number><name>User Nickname</name><type>Standards Track</type><status>Draft</status><updated>2006-06-05</updated><shortname>nick</shortname><abstract>This specification defines a protocol for communicating user nicknames, either in XMPP presence subscription requests or in XMPP messages.</abstract></xep>
<xep><number>0173</number><name>Pubsub Subscription Storage</name><type>Historical</type><status>Deferred</status><updated>2006-02-09</updated><shortname>pubsubs</shortname><abstract>This document defines an XMPP protocol extension for storing subscriptions to Pubsub nodes.</abstract></xep>
<xep><number>0174</number><name>Serverless Messaging</name><type>Standards Track</type><status>Final</status><updated>2008-11-26</updated><shortname>linklocal</shortname><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></xep>
<xep><number>0175</number><name>Best Practices for Use of SASL ANONYMOUS</name><type>Informational</type><status>Active</status><updated>2009-09-30</updated><shortname>N/A</shortname><abstract>This document specifies best practices for use of the SASL ANONYMOUS mechanism in the context of client authentication with an XMPP server.</abstract></xep>
<xep><number>0176</number><name>Jingle ICE-UDP Transport Method</name><type>Standards Track</type><status>Draft</status><updated>2009-06-10</updated><shortname>jingle-ice-udp</shortname><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></xep>
<xep><number>0177</number><name>Jingle Raw UDP Transport Method</name><type>Standards Track</type><status>Draft</status><updated>2009-12-23</updated><shortname>jingle-raw-udp</shortname><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></xep>
<xep><number>0178</number><name>Best Practices for Use of SASL EXTERNAL with Certificates</name><type>Informational</type><status>Active</status><updated>2011-05-25</updated><shortname>N/A</shortname><abstract>This document specifies best practices for XMPP usage of the SASL EXTERNAL mechanism in the context of PKIX certificates.</abstract></xep>
<xep><number>0179</number><name>Jingle IAX Transport Method</name><type>Standards Track</type><status>Deferred</status><updated>2006-03-23</updated><shortname>jingle-iax</shortname><abstract>This document defines a Jingle transport method that results in using the Inter-Asterisk eXchange protocol (IAX) for the final communication.</abstract></xep>
<xep><number>0180</number><name>Jingle Video via RTP</name><type>Standards Track</type><status>Retracted</status><updated>2008-06-04</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>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></xep>
<xep><number>0181</number><name>Jingle DTMF</name><type>Standards Track</type><status>Deferred</status><updated>2009-10-02</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0182</number><name>Application-Specific Error Conditions</name><type>Procedural</type><status>Active</status><updated>2008-03-05</updated><shortname>errors</shortname><abstract>This document defines a registry of application-specific error conditions.</abstract></xep>
<xep><number>0183</number><name>Jingle Telepathy Transport</name><type>Humorous</type><status>Active</status><updated>2006-04-01</updated><shortname>telepathy</shortname><abstract>This document defines a telepathic transport method for establishing Extra-Sensory Perception (ESP) streams.</abstract></xep>
<xep><number>0184</number><name>Message Delivery Receipts</name><type>Standards Track</type><status>Draft</status><updated>2011-03-01</updated><shortname>receipts</shortname><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></xep>
<xep><number>0185</number><name>Dialback Key Generation and Validation</name><type>Informational</type><status>Active</status><updated>2007-02-15</updated><shortname>N/A</shortname><abstract>This document provides a recommended method for generating and validating the keys used in the XMPP server dialback protocol.</abstract></xep>
<xep><number>0186</number><name>Invisible Command</name><type>Standards Track</type><status>Deferred</status><updated>2008-10-07</updated><shortname>invisible</shortname><abstract>This document specifies an XMPP-compatible protocol for user invisibility.</abstract></xep>
<xep><number>0187</number><name>Offline Encrypted Sessions</name><type>Standards Track</type><status>Deferred</status><updated>2007-05-30</updated><shortname>TO BE ASSIGNED</shortname><abstract>This document specifies an end-to-end encryption protocol for offline XMPP communication sessions.</abstract></xep>
<xep><number>0188</number><name>Cryptographic Design of Encrypted Sessions</name><type>Informational</type><status>Deferred</status><updated>2007-05-30</updated><shortname>N/A</shortname><abstract>This document describes the cryptographic design that underpins the XMPP protocol extensions Encrypted Session Negotiation, Offline Encrypted Sessions and Stanza Encryption.</abstract></xep>
<xep><number>0189</number><name>Public Key Publishing</name><type>Standards Track</type><status>Deferred</status><updated>2010-07-15</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a method by which an entity can publish its public keys over XMPP.</abstract></xep>
<xep><number>0190</number><name>Best Practice for Closing Idle Streams</name><type>Informational</type><status>Active</status><updated>2007-01-04</updated><shortname>N/A</shortname><abstract>This document specifies a best practice for closing an XML stream that is perceived to be idle.</abstract></xep>
<xep><number>0191</number><name>Simple Communications Blocking</name><type>Standards Track</type><status>Draft</status><updated>2007-02-15</updated><shortname>blocking</shortname><abstract>This document specifies an XMPP protocol extension for simple communications blocking.</abstract></xep>
<xep><number>0192</number><name>Proposed Stream Feature Improvements</name><type>Standards Track</type><status>Deprecated</status><updated>2011-05-11</updated><shortname>N/A</shortname><abstract>This document proposes improvements to the XML stream features definition for inclusion in the specification that supersedes RFC 3920.</abstract></xep>
<xep><number>0193</number><name>Proposed Resource Binding Improvements</name><type>Standards Track</type><status>Deprecated</status><updated>2011-05-11</updated><shortname>N/A</shortname><abstract>This document proposes improvements to the definition of resource binding for inclusion in the specification that supersedes RFC 3920.</abstract></xep>
<xep><number>0194</number><name>User Chatting</name><type>Standards Track</type><status>Deferred</status><updated>2008-09-25</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines an XMPP protocol extension for communicating information about the chatrooms a user visits.</abstract></xep>
<xep><number>0195</number><name>User Browsing</name><type>Standards Track</type><status>Deferred</status><updated>2008-09-25</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document defines an XMPP protocol extension for communicating information about the web pages a user visits.</abstract></xep>
<xep><number>0196</number><name>User Gaming</name><type>Standards Track</type><status>Deferred</status><updated>2008-09-25</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document defines an XMPP protocol extension for communicating information about the games a user plays.</abstract></xep>
<xep><number>0197</number><name>User Viewing</name><type>Standards Track</type><status>Deferred</status><updated>2008-09-25</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document defines an XMPP protocol extension for communicating information about the television shows, movies, or other videos that a user watches.</abstract></xep>
<xep><number>0198</number><name>Stream Management</name><type>Standards Track</type><status>Draft</status><updated>2011-06-29</updated><shortname>sm</shortname><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></xep>
<xep><number>0199</number><name>XMPP Ping</name><type>Standards Track</type><status>Final</status><updated>2009-06-03</updated><shortname>ping</shortname><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></xep>
<xep><number>0200</number><name>Stanza Encryption</name><type>Standards Track</type><status>Deferred</status><updated>2007-05-30</updated><shortname>TO BE ASSIGNED</shortname><abstract>This document specifies an XMPP protocol extension for session-based stanza encryption.</abstract></xep>
<xep><number>0201</number><name>Best Practices for Message Threads</name><type>Informational</type><status>Active</status><updated>2010-11-29</updated><shortname>N/A</shortname><abstract>This specification defines recommended handling of XMPP message threads.</abstract></xep>
<xep><number>0202</number><name>Entity Time</name><type>Standards Track</type><status>Final</status><updated>2009-09-11</updated><shortname>time</shortname><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></xep>
<xep><number>0203</number><name>Delayed Delivery</name><type>Standards Track</type><status>Final</status><updated>2009-09-15</updated><shortname>delay</shortname><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></xep>
<xep><number>0204</number><name>Collaborative Data Objects</name><type>Standards Track</type><status>Deferred</status><updated>2007-01-17</updated><shortname>TO BE ISSUED</shortname><abstract>This document specifies an XMPP protocol extension that supports the exchange of structured data objects.</abstract></xep>
<xep><number>0205</number><name>Best Practices to Discourage Denial of Service Attacks</name><type>Informational</type><status>Active</status><updated>2009-01-07</updated><shortname>N/A</shortname><abstract>This document recommends a number of practices that can help discourage denial of service attacks on XMPP-based networks.</abstract></xep>
<xep><number>0206</number><name>XMPP Over BOSH</name><type>Standards Track</type><status>Draft</status><updated>2010-07-02</updated><shortname>xbosh</shortname><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></xep>
<xep><number>0207</number><name>XMPP Eventing via Pubsub</name><type>Humorous</type><status>Active</status><updated>2007-04-01</updated><shortname>N/A</shortname><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></xep>
<xep><number>0208</number><name>Bootstrapping Implementation of Jingle</name><type>Informational</type><status>Retracted</status><updated>2009-01-06</updated><shortname>N/A</shortname><abstract>This document provides guidelines to XMPP client developers for bootstrapping implementation of Jingle technologies.</abstract></xep>
<xep><number>0209</number><name>Metacontacts</name><type>Standards Track</type><status>Deferred</status><updated>2007-04-10</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This document specifies an XMPP protocol extension for defining metacontacts and grouping member JIDs.</abstract></xep>
<xep><number>0210</number><name>Requirements for Encrypted Sessions</name><type>Standards Track</type><status>Deferred</status><updated>2007-05-30</updated><shortname>N/A</shortname><abstract>This document describes the requirements for an XMPP end-to-end encrypted session protocol.</abstract></xep>
<xep><number>0211</number><name>XMPP Basic Client 2008</name><type>Standards Track</type><status>Obsolete</status><updated>2007-07-11</updated><shortname>N/A</shortname><abstract>This document defines the XMPP Basic Client 2008 compliance level.</abstract></xep>
<xep><number>0212</number><name>XMPP Basic Server 2008</name><type>Standards Track</type><status>Obsolete</status><updated>2007-07-11</updated><shortname>N/A</shortname><abstract>This document defines the XMPP Basic Server 2008 compliance level.</abstract></xep>
<xep><number>0213</number><name>XMPP Intermediate IM Client 2008</name><type>Standards Track</type><status>Obsolete</status><updated>2007-07-11</updated><shortname>N/A</shortname><abstract>This document defines the XMPP Intermediate IM Client 2008 compliance level.</abstract></xep>
<xep><number>0214</number><name>File Repository and Sharing</name><type>Standards Track</type><status>Deferred</status><updated>2009-01-05</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0215</number><name>External Service Discovery</name><type>Standards Track</type><status>Deferred</status><updated>2010-02-17</updated><shortname>extdisco</shortname><abstract>This document specifies an XMPP protocol extension for discovering services external to the XMPP network.</abstract></xep>
<xep><number>0216</number><name>XMPP Intermediate IM Server 2008</name><type>Standards Track</type><status>Obsolete</status><updated>2007-07-11</updated><shortname>N/A</shortname><abstract>This document defines the XMPP Intermedate IM Server 2008 compliance level.</abstract></xep>
<xep><number>0217</number><name>Simplified Encrypted Session Negotiation</name><type>Standards Track</type><status>Deferred</status><updated>2007-05-30</updated><shortname>TO BE ASSIGNED</shortname><abstract>This document specifies a minimal subset of the Encrypted Session Negotiation protocol sufficent for negotiating an end-to-end encrypted session.</abstract></xep>
<xep><number>0218</number><name>Bootstrapping Implementation of Encrypted Sessions</name><type>Informational</type><status>Deferred</status><updated>2007-05-30</updated><shortname>N/A</shortname><abstract>This document provides guidelines to client and library developers for bootstrapping implementation of the encrypted sessions technology.</abstract></xep>
<xep><number>0219</number><name>Hop Check</name><type>Standards Track</type><status>Retracted</status><updated>2008-06-12</updated><shortname>TO BE ASSIGNED</shortname><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></xep>
<xep><number>0220</number><name>Server Dialback</name><type>Standards Track</type><status>Experimental</status><updated>2011-09-19</updated><shortname>dialback</shortname><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 originating server, it does not process traffic over the connection until it has verified a key with an authoritative server for the domain asserted by the originating server. Although Server Dialback does not provide strong authentication or trusted federation and although it is subject to DNS poisoning attacks, it has effectively prevented most instances of address spoofing on the XMPP network since its development in the year 2000.</abstract></xep>
<xep><number>0221</number><name>Data Forms Media Element</name><type>Standards Track</type><status>Draft</status><updated>2008-09-03</updated><shortname>media-element</shortname><abstract>This specification defines an XMPP protocol extension for including media data in XEP-0004 data forms.</abstract></xep>
<xep><number>0222</number><name>Persistent Storage of Public Data via PubSub</name><type>Informational</type><status>Active</status><updated>2008-09-08</updated><shortname>N/A</shortname><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></xep>
<xep><number>0223</number><name>Persistent Storage of Private Data via PubSub</name><type>Informational</type><status>Active</status><updated>2008-09-08</updated><shortname>N/A</shortname><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></xep>
<xep><number>0224</number><name>Attention</name><type>Standards Track</type><status>Draft</status><updated>2008-11-13</updated><shortname>attention</shortname><abstract>This document defines an XMPP protocol extension for getting the attention of another user.</abstract></xep>
<xep><number>0225</number><name>Component Connections</name><type>Standards Track</type><status>Deferred</status><updated>2008-10-06</updated><shortname>component</shortname><abstract>This document specifies a standards-track XMPP protocol extension that enables server components to connect to XMPP servers.</abstract></xep>
<xep><number>0226</number><name>Message Stanza Profiles</name><type>Informational</type><status>Deferred</status><updated>2008-11-05</updated><shortname>profiles</shortname><abstract>This document specifies best practices for generating and handling extended content in XMPP message stanzas.</abstract></xep>
<xep><number>0227</number><name>Portable Import/Export Format for XMPP-IM Servers</name><type>Standards Track</type><status>Draft</status><updated>2010-03-12</updated><shortname>pie</shortname><abstract>This document specifies a file format for importing and exporting user data to and from XMPP-IM servers.</abstract></xep>
<xep><number>0228</number><name>Requirements for Shared Editing</name><type>Standards Track</type><status>Deferred</status><updated>2007-08-22</updated><shortname>N/A</shortname><abstract>This document defines requirements for the design of XMPP-based shared editing protocols.</abstract></xep>
<xep><number>0229</number><name>Stream Compression with LZW</name><type>Standards Track</type><status>Draft</status><updated>2007-09-26</updated><shortname>N/A</shortname><abstract>This document specifies how to use the LZW algorithm in XML stream compression.</abstract></xep>
<xep><number>0230</number><name>Service Discovery Notifications</name><type>Standards Track</type><status>Deferred</status><updated>2008-01-30</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This specification defines a method for requesting and receiving notifications regarding XMPP service discovery items.</abstract></xep>
<xep><number>0231</number><name>Bits of Binary</name><type>Standards Track</type><status>Draft</status><updated>2008-09-03</updated><shortname>bob</shortname><abstract>This specification defines an XMPP protocol extension for including or referring to small bits of binary data in an XML stanza.</abstract></xep>
<xep><number>0232</number><name>Software Information</name><type>Standards Track</type><status>Deferred</status><updated>2009-02-26</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0233</number><name>Domain-Based Service Names in XMPP SASL Negotiation</name><type>Standards Track</type><status>Experimental</status><updated>2011-08-26</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This specification defines a method by a connecting client can learn the domain-based service name of a Kerberos acceptor principal for SASL authentication using the GSSAPI mechanism.</abstract></xep>
<xep><number>0234</number><name>Jingle File Transfer</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-29</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a Jingle application type 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></xep>
<xep><number>0235</number><name>OAuth Over XMPP</name><type>Standards Track</type><status>Deferred</status><updated>2009-03-24</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines an XMPP extension for delegating access to protected resources over XMPP, using the OAuth protocol.</abstract></xep>
<xep><number>0236</number><name>Abuse Reporting</name><type>Standards Track</type><status>Retracted</status><updated>2008-05-09</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0237</number><name>Roster Versioning</name><type>Standards Track</type><status>Draft</status><updated>2011-03-16</updated><shortname>N/A</shortname><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></xep>
<xep><number>0238</number><name>XMPP Protocol Flows for Inter-Domain Federation</name><type>Informational</type><status>Deferred</status><updated>2008-03-31</updated><shortname>N/A</shortname><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></xep>
<xep><number>0239</number><name>Binary XMPP</name><type>Humorous</type><status>Active</status><updated>2008-04-01</updated><shortname>N/A</shortname><abstract>This specification defines Binary XMPP, an obviously superior representation of the Extensible Messaging and Presence Protocol (XMPP).</abstract></xep>
<xep><number>0240</number><name>Auto-Discovery of JabberIDs</name><type>Standards Track</type><status>Deferred</status><updated>2008-04-30</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a recommended best practice for linking to JabberIDs from documents hosted on the World Wide Web.</abstract></xep>
<xep><number>0241</number><name>Encryption of Archived Messages</name><type>Standards Track</type><status>Deferred</status><updated>2008-04-30</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines methods for encrypting messages that are archived at an XMPP server.</abstract></xep>
<xep><number>0242</number><name>XMPP Client Compliance 2009</name><type>Standards Track</type><status>Draft</status><updated>2008-09-08</updated><shortname>N/A</shortname><abstract>This document defines XMPP client compliance levels for 2009.</abstract></xep>
<xep><number>0243</number><name>XMPP Server Compliance 2009</name><type>Standards Track</type><status>Draft</status><updated>2008-09-08</updated><shortname>N/A</shortname><abstract>This document defines XMPP server compliance levels for 2009.</abstract></xep>
<xep><number>0244</number><name>IO Data</name><type>Standards Track</type><status>Deferred</status><updated>2008-06-18</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines an XMPP protocol extension for handling the input to and output from a remote entity.</abstract></xep>
<xep><number>0245</number><name>The /me Command</name><type>Informational</type><status>Active</status><updated>2009-01-21</updated><shortname>N/A</shortname><abstract>This specification defines recommended handling of the /me command in XMPP instant messaging clients.</abstract></xep>
<xep><number>0246</number><name>End-to-End XML Streams</name><type>Standards Track</type><status>Deferred</status><updated>2008-06-18</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0247</number><name>Jingle XML Streams</name><type>Standards Track</type><status>Deferred</status><updated>2009-02-20</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0248</number><name>PubSub Collection Nodes</name><type>Standards Track</type><status>Deferred</status><updated>2010-09-28</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines the nature and handling of collection nodes in the XMPP publish-subscribe extension.</abstract></xep>
<xep><number>0249</number><name>Direct MUC Invitations</name><type>Standards Track</type><status>Draft</status><updated>2011-09-22</updated><shortname>x-conference</shortname><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></xep>
<xep><number>0250</number><name>C2C Authentication Using TLS</name><type>Standards Track</type><status>Deferred</status><updated>2008-09-08</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0251</number><name>Jingle Session Transfer</name><type>Standards Track</type><status>Deferred</status><updated>2009-10-05</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines an extension to XMPP Jingle for transferring a session (such as a voice call) from one person to another.</abstract></xep>
<xep><number>0252</number><name>BOSH Script Syntax</name><type>Historical</type><status>Deferred</status><updated>2008-10-31</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification provides historical documentation regarding the &quot;alternative script syntax&quot; first defined in Version 1.6 of XEP-0124.</abstract></xep>
<xep><number>0253</number><name>PubSub Chaining</name><type>Standards Track</type><status>Deferred</status><updated>2009-11-18</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a method for chaining pubsub nodes together, resulting in lightweight repeaters for pubsub notifications.</abstract></xep>
<xep><number>0254</number><name>PubSub Queueing</name><type>Standards Track</type><status>Deferred</status><updated>2008-11-13</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines an extension to XMPP publish-subscribe for queueing information at a node.</abstract></xep>
<xep><number>0255</number><name>Location Query</name><type>Standards Track</type><status>Deferred</status><updated>2009-04-09</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0256</number><name>Last Activity in Presence</name><type>Standards Track</type><status>Draft</status><updated>2009-09-15</updated><shortname>N/A</shortname><abstract>This specification defines a way to use the Last Activity extension in XMPP presence notifications.</abstract></xep>
<xep><number>0257</number><name>Client Certificate Management for SASL EXTERNAL</name><type>Standards Track</type><status>Deferred</status><updated>2009-02-12</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0258</number><name>Security Labels in XMPP</name><type>Standards Track</type><status>Draft</status><updated>2011-11-10</updated><shortname>sec-label</shortname><abstract>This document describes the use of security labels in XMPP. The document specifies
            how security label meta-data is carried in XMPP, when this meta-data should or should
            not be provided, and how the meta-data is to be processed.</abstract></xep>
<xep><number>0259</number><name>Message Mine-ing</name><type>Standards Track</type><status>Deferred</status><updated>2009-01-21</updated><shortname>mine</shortname><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></xep>
<xep><number>0260</number><name>Jingle SOCKS5 Bytestreams Transport Method</name><type>Standards Track</type><status>Draft</status><updated>2011-09-23</updated><shortname>jingle-s5b</shortname><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></xep>
<xep><number>0261</number><name>Jingle In-Band Bytestreams Transport Method</name><type>Standards Track</type><status>Draft</status><updated>2011-09-23</updated><shortname>jingle-ibb</shortname><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></xep>
<xep><number>0262</number><name>Use of ZRTP in Jingle RTP Sessions</name><type>Standards Track</type><status>Draft</status><updated>2011-06-15</updated><shortname>jingle-zrtp</shortname><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></xep>
<xep><number>0263</number><name>ECO-XMPP</name><type>Humorous</type><status>Active</status><updated>2009-04-01</updated><shortname>eco-xmpp</shortname><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></xep>
<xep><number>0264</number><name>File Transfer Thumbnails</name><type>Standards Track</type><status>Deferred</status><updated>2009-04-27</updated><shortname>thumbs</shortname><abstract>This specification defines a way for a client supply a preview image for a file transfer.</abstract></xep>
<xep><number>0265</number><name>Out-of-Band Stream Data</name><type>Standards Track</type><status>Deferred</status><updated>2009-04-02</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0266</number><name>Codecs for Jingle Audio</name><type>Standards Track</type><status>Draft</status><updated>2011-10-04</updated><shortname>N/A</shortname><abstract>This document describes implementation considerations related to audio codecs for use in Jingle RTP sessions.</abstract></xep>
<xep><number>0267</number><name>Server Buddies</name><type>Standards Track</type><status>Experimental</status><updated>2011-12-12</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a convention for presence subscriptions between XMPP servers.</abstract></xep>
<xep><number>0268</number><name>Incident Reporting</name><type>Standards Track</type><status>Deferred</status><updated>2009-11-17</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines methods for incident reporting among XMPP server deployments.</abstract></xep>
<xep><number>0269</number><name>Jingle Early Media</name><type>Standards Track</type><status>Deferred</status><updated>2009-05-19</updated><shortname>N/A</shortname><abstract>This specification describes methods for exchanging early media in the context of Jingle RTP sessions.</abstract></xep>
<xep><number>0270</number><name>XMPP Compliance Suites 2010</name><type>Standards Track</type><status>Draft</status><updated>2009-09-30</updated><shortname>N/A</shortname><abstract>This document defines XMPP protocol compliance levels for 2010.</abstract></xep>
<xep><number>0271</number><name>XMPP Nodes</name><type>Informational</type><status>Deferred</status><updated>2009-06-26</updated><shortname>N/A</shortname><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></xep>
<xep><number>0272</number><name>Multiparty Jingle (Muji)</name><type>Standards Track</type><status>Deferred</status><updated>2009-09-11</updated><shortname>muji</shortname><abstract>
    This specification defines an XMPP protocol extension for initiating and
    managing multiparty voice and video conferences within an XMPP MUC
  </abstract></xep>
<xep><number>0273</number><name>Stanza Interception and Filtering Technology (SIFT)</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-27</updated><shortname>sift</shortname><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></xep>
<xep><number>0274</number><name>Design Considerations for Digital Signatures in XMPP</name><type>Informational</type><status>Experimental</status><updated>2011-01-28</updated><shortname>N/A</shortname><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></xep>
<xep><number>0275</number><name>Entity Reputation</name><type>Standards Track</type><status>Deferred</status><updated>2010-01-21</updated><shortname>reputation</shortname><abstract>This specification defines an XMPP protocol extension for communicating the reputation of any entity on the network.</abstract></xep>
<xep><number>0276</number><name>Temporary Presence Sharing</name><type>Standards Track</type><status>Deferred</status><updated>2010-01-26</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0277</number><name>Microblogging over XMPP</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-15</updated><shortname>microblog</shortname><abstract>This specification defines a method for microblogging over XMPP.</abstract></xep>
<xep><number>0278</number><name>Jingle Relay Nodes</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-21</updated><shortname>jinglenodes</shortname><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></xep>
<xep><number>0279</number><name>Server IP Check</name><type>Standards Track</type><status>Deferred</status><updated>2010-03-05</updated><shortname>sic</shortname><abstract>This specification defines a simple XMPP extension that enables a client to discover its external IP address.</abstract></xep>
<xep><number>0280</number><name>Message Carbons</name><type>Standards Track</type><status>Experimental</status><updated>2012-01-06</updated><shortname>carbons</shortname><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></xep>
<xep><number>0281</number><name>DMUC1: Distributed Multi-User Chat</name><type>Standards Track</type><status>Deferred</status><updated>2010-07-20</updated><shortname>NOT-YET-ASSIGNED</shortname><abstract>This document defines methods for distributing Multi-User Chat (MUC) rooms across multiple chat services.</abstract></xep>
<xep><number>0282</number><name>DMUC2: Distributed MUC</name><type>Standards Track</type><status>Deferred</status><updated>2010-06-11</updated><shortname>NOT-YET-ASSIGNED</shortname><abstract>Multi-User Chats, distributed over several nodes in the XMPP network, using a master/slave architecture</abstract></xep>
<xep><number>0283</number><name>Moved</name><type>Standards Track</type><status>Deferred</status><updated>2010-06-16</updated><shortname>moved</shortname><abstract>This document defines an XMPP protocol extension that enables a user to inform its contacts about a change in JID.</abstract></xep>
<xep><number>0284</number><name>Shared XML Editing</name><type>Standards Track</type><status>Deferred</status><updated>2010-07-02</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0285</number><name>Encapsulating Digital Signatures in XMPP</name><type>Standards Track</type><status>Experimental</status><updated>2011-01-12</updated><shortname>N/A</shortname><abstract>This document provides a technical specification for Encapsulating Digital Signatures
      in the Extensible Messaging and Presence Protocol (XMPP).</abstract></xep>
<xep><number>0286</number><name>XMPP on Mobile Devices</name><type>Informational</type><status>Deferred</status><updated>2010-09-15</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document provides background information for XMPP implementors concerned with mobile devices operating in a cellular network such as 3G.</abstract></xep>
<xep><number>0287</number><name>Spim Markers and Reports</name><type>Standards Track</type><status>Deferred</status><updated>2010-10-04</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0288</number><name>Bidirectional Server-to-Server Connections</name><type>Standards Track</type><status>Experimental</status><updated>2011-12-12</updated><shortname>bidi</shortname><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></xep>
<xep><number>0289</number><name>Federated MUC for Constrained Environments</name><type>Standards Track</type><status>Experimental</status><updated>2010-11-29</updated><shortname>FMUC</shortname><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></xep>
<xep><number>0290</number><name>Encapsulated Digital Signatures in XMPP</name><type>Standards Track</type><status>Experimental</status><updated>2011-01-28</updated><shortname>N/A</shortname><abstract>This document provides a technical specification for Encapsulated Digital
            Signatures in the Extensible Messaging and Presence Protocol (XMPP).</abstract></xep>
<xep><number>0291</number><name>Service Delegation</name><type>Standards Track</type><status>Experimental</status><updated>2011-01-26</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines an approach for users to delegate certain services (e.g. pubsub) to alternative JIDs.</abstract></xep>
<xep><number>0292</number><name>vCard4 Over XMPP</name><type>Standards Track</type><status>Experimental</status><updated>2011-10-09</updated><shortname>NOT_YET_ASSIGNED</shortname><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></xep>
<xep><number>0293</number><name>Jingle RTP Feedback Negotiation</name><type>Standards Track</type><status>Experimental</status><updated>2011-03-24</updated><shortname>NOT YET ASSIGNED</shortname><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></xep>
<xep><number>0294</number><name>Jingle RTP Header Extensions Negotiation</name><type>Standards Track</type><status>Experimental</status><updated>2011-03-24</updated><shortname>NOT YET ASSIGNED</shortname><abstract>This specification defines an XMPP extension to negotiate
  the use of the use of RTP Header Extension as defined by RFC 5285
  with Jingle RTP sessions</abstract></xep>
<xep><number>0295</number><name>JSON Encodings for XMPP</name><type>Humorous</type><status>Active</status><updated>2011-04-01</updated><shortname>N/A</shortname><abstract>This specification defines an alternative JSON encoding for XMPP stanzas and other elements.</abstract></xep>
<xep><number>0296</number><name>Best Practices for Resource Locking</name><type>Informational</type><status>Experimental</status><updated>2011-08-18</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This document specifies best practices to be followed by Jabber/XMPP clients about when to lock into, and unlock away from, resources.</abstract></xep>
<xep><number>0297</number><name>Message Forwarding</name><type>Standards Track</type><status>Experimental</status><updated>2011-07-11</updated><shortname>forwarding</shortname><abstract>This document defines a protocol to forward a message from one entity to another.</abstract></xep>
<xep><number>0298</number><name>Delivering Conference Information to Jingle Participants (Coin)</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-09</updated><shortname>coin</shortname><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></xep>
<xep><number>0299</number><name>Codecs for Jingle Video</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-12</updated><shortname>N/A</shortname><abstract>This document describes implementation considerations related to video codecs for use in Jingle RTP sessions.</abstract></xep>
<xep><number>0300</number><name>Use of Cryptographic Hash Functions in XMPP</name><type>Standards Track</type><status>Experimental</status><updated>2011-12-05</updated><shortname>N/A</shortname><abstract>This document provides recommendations for the use of cryptographic hash functions in XMPP protocol extensions.</abstract></xep>
<xep><number>0301</number><name>In-Band Real Time Text</name><type>Standards Track</type><status>Experimental</status><updated>2011-06-29</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This is a specification for real-time text transmitted in-band over an XMPP session.</abstract></xep>
<xep><number>0302</number><name>XMPP Compliance Suites 2012</name><type>Standards Track</type><status>Experimental</status><updated>2011-07-21</updated><shortname>N/A</shortname><abstract>This document defines XMPP protocol compliance levels for 2012.</abstract></xep>
<xep><number>0303</number><name>Commenting</name><type>Standards Track</type><status>Experimental</status><updated>2011-07-28</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a method for commenting.</abstract></xep>
<xep><number>0304</number><name>Whitespace Keepalive Negotiation</name><type>Standards Track</type><status>Experimental</status><updated>2011-08-18</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a method for negotiating how to send keepalives in XMPP.</abstract></xep>
<xep><number>0305</number><name>XMPP Quickstart</name><type>Standards Track</type><status>Experimental</status><updated>2011-08-25</updated><shortname>N/A</shortname><abstract>This document defines methods for speeding the process of connecting or reconnecting to an XMPP.</abstract></xep>
<xep><number>0306</number><name>Extensible Status Conditions for Multi-User Chat</name><type>Standards Track</type><status>Experimental</status><updated>2011-12-14</updated><shortname>N/A</shortname><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></xep>
<xep><number>0307</number><name>Unique Room Names for Multi-User Chat</name><type>Standards Track</type><status>Experimental</status><updated>2011-11-10</updated><shortname>muc-unique</shortname><abstract>This specification defines an XMPP protocol extension for requesting a unique room ID from a multi-user chat service.</abstract></xep>
<xep><number>0308</number><name>Last Message Correction</name><type>Standards Track</type><status>Experimental</status><updated>2011-11-10</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification defines a method for marking a message as a correction of the last sent message.</abstract></xep>
<xep><number>0309</number><name>Service Directories</name><type>Standards Track</type><status>Experimental</status><updated>2012-01-25</updated><shortname>NOT_YET_ASSIGNED</shortname><abstract>This specification shows how to combine and extend a number of existing XMPP protocols for improved sharing of information about XMPP servers.</abstract></xep>
<xep><number>0310</number><name>Presence State Annotations</name><type>Standards Track</type><status>Experimental</status><updated>2012-01-10</updated><shortname>PSA</shortname><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></xep>
<xep><number>0311</number><name>MUC Fast Reconnect</name><type>Standards Track</type><status>Experimental</status><updated>2012-01-25</updated><shortname>MFR</shortname><abstract>This document provides a protocol that can be used for limiting the amount of presence history needed when rejoining a MUC room.</abstract></xep>
</xeps>
