You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

176 lines
7.4 KiB

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title>Legacy Delayed Delivery</title>
<abstract>This specification provides historical documentation of the legacy jabber:x:delay namespace, which has been deprecated in favor the urn:xmpp:delay namespace defined in XEP-0203.</abstract>
<spec>XMPP Core</spec>
<remark>Per a vote of the XMPP Council, changed status to Obsolete.</remark>
<remark><p>Per a vote of the XMPP Council, deprecated in favor of XEP-0203.</p></remark>
<remark><p>Specified that the timezone is to be understood as UTC; specified security considerations; corrected several small textual errors.</p></remark>
<remark><p>Corrected several small textual errors.</p></remark>
<remark><p>Per a vote of the Jabber Council, changed status to Active.</p></remark>
<remark><p>Initial version.</p></remark>
<section1 topic='Introduction' anchor='intro'>
<p class='note'>Note: This specification has been deprecated in favor of &xep0203;.</p>
<p>This document provides canonical documentation of the 'jabber:x:delay' namespace, which was long used by Jabber applications to mark message or presence stanzas as delivered with a delay. This document is of historical importance only, since it has been deprecated in favor of <cite>XEP-0203</cite>.</p>
<section1 topic='Protocol Definition' anchor='protocol'>
<p>The 'jabber:x:delay' namespace is used to provide timestamp information about data stored for later delivery. The most common uses of this namespace are to stamp:</p>
<li>A message that is sent to an offline entity and stored for later delivery.</li>
<li>The last presence update sent by a connected node to a host.</li>
<li>Messages cached by a multi-user chat room for delivery to new participants when they join the room.</li>
<p>Information about the delivery delay is communicated by adding to the &lt;message/&gt; or &lt;presence/&gt; stanza one and only one &lt;x/&gt; child qualified by the 'jabber:x:delay' namespace. This information is added by the server or component that delivers the information. The following attributes are allowed on the &lt;x/&gt; element:</p>
<li><cite>from</cite> -- The Jabber ID of the entity that originally sent the XML stanza or that delayed the delivery of the stanza (for example, the address of a multi-user chat room). This attribute is RECOMMENDED.</li>
<li><cite>stamp</cite> -- The time when the XML stanza was originally sent. The format SHOULD be "CCYYMMDDThh:mm:ss" (see <link url="#time">A Note on Time Formats</link> below). This attribute is REQUIRED.</li>
<p>In addition, the &lt;x/&gt; element MAY contain XML character data that provides a natural-language description of the reason for the delay.</p>
<section1 topic='Examples' anchor='examples'>
<example caption='Receiving a Message Sent While Offline'><![CDATA[
O blessed, blessed night! I am afeard.
Being in night, all this is but a dream,
Too flattering-sweet to be substantial.
<x xmlns='jabber:x:delay'
Offline Storage
<example caption='Receiving the Last Presence Update of Another Entity'><![CDATA[
<presence from='' to=''>
<x xmlns='jabber:x:delay'
<example caption='Receiving Cached Messages from a Conference Room'><![CDATA[
By the pricking of my thumbs,
Something wicked this way comes.
Open, locks,
Whoever knocks!
<x xmlns='jabber:x:delay'
<section1 topic='A Note on Time Formats' anchor='time'>
<p>&xep0082; defines the lexical representation of dates, times, and datetimes in Jabber protocols. Unfortunately, the 'jabber:x:delay' namespace predates that definition, and uses a datetime format ("CCYYMMDDThh:mm:ss") that is inconsistent with XEP-0082 and &w3xmlschema2;. Because a large base of deployed software uses the old format, this document specifies that applications using 'jabber:x:delay' SHOULD use the old format, not the format defined in XEP-0082. The timezone is be understood as UTC.</p>
<section1 topic='Security Considerations' anchor='security'>
<p>Data qualified by the 'jabber:x:delay' can expose information about the sender's presence on the network at some time in the past. However, this introduces no new vulnerabilities, since the same information would have been available in real time.</p>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>The 'jabber:x:delay' namespace is included in the protocol namespaces registry maintained by the &REGISTRAR;.</p>
<section1 topic='XML Schema' anchor='schema'>
<?xml version='1.0' encoding='UTF-8'?>
The protocol documented by this schema is defined in
NOTE: This protocol has been deprecated in favor of the
Delayed Delivery protocol specified in XEP-0203:
<xs:element name='x'>
<xs:extension base='xs:string'>
<xs:attribute name='from' type='xs:string' use='optional'/>
<xs:attribute name='stamp' type='xs:string' use='required'/>