moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 02:32:18 -05:00
Code Issues Releases Wiki Activity
ea3977b83e
xeps/inbox/message-retraction.xml

168 lines
8.6 KiB
XML
Raw Normal View History

Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
Change title to Message Retraction
2016-10-19 11:18:40 -04:00
<title>Message Retraction</title>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<abstract>This specification defines a method for indicating that a message should be retracted.</abstract>
&LEGALNOTICE;
<number>XXXX</number>
<status>Experimental</status>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>XMPP Core</spec>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<spec>XMPP IM</spec>
<spec>XEP-0313</spec>
<spec>XEP-0421</spec>
<spec>XEP-0422</spec>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</dependencies>
<supersedes/>
<supersededby/>
<shortname>message-retract</shortname>
&lance;
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
&jcbrand;
<revision>
<version>0.0.4</version>
<date>2019-09-25</date>
<initials>jcb</initials>
<remark><p>Remove MUC moderation use-case which will go into a separate XEP</p></remark>
</revision>
Change title to Message Retraction
2016-10-19 11:18:40 -04:00
<revision>
Fix version number
2016-10-19 17:29:03 -04:00
<version>0.0.3</version>
Change title to Message Retraction
2016-10-19 11:18:40 -04:00
<date>2016-10-19</date>
<initials>ljts</initials>
<remark><p>Fix the XEP title to be Message Retraction.</p></remark>
</revision>
Update revisions
2016-10-12 13:44:32 -04:00
<revision>
<version>0.0.2</version>
<date>2016-10-12</date>
<initials>ljts</initials>
<remark><p>Use the term 'retraction' instead of 'deletion'. Added tombstone marker.</p></remark>
</revision>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<revision>
<version>0.0.1</version>
<date>2015-07-07</date>
<initials>ljts</initials>
<remark><p>First draft.</p></remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>A chat participant might want to retract a message which they've already sent out, for example if they've mistakenly sent it to the wrong recipient or groupchat.</p>
<p>Due to the federated and extensible nature of XMPP it's not possible to remove a message with full certainty and a retraction can only be considered an <strong>unenforceable request</strong> for such removal. Clients which don't support message retraction are not obligated to enforce the request and people could have seen or copied the message contents already.</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</section1>
<section1 topic='Discovering support' anchor='disco'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>If a client or service implements message retraction, it MUST specify the 'urn:xmpp:message-retract:0' feature in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<example caption='Client requests information about a chat partner&apos;s client'><![CDATA[
<iq type='get'
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
from='romeo@montague.example/orchard'
to='juliet@capulet.example/balcony'
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
id='info1'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>]]></example>
<example caption='Partner&apos;s client advertises support for retraction'><![CDATA[
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<iq type='result'
to='romeo@montague.example/orchard'
from='juliet@capulet.example/balcony'
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
id='info1'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='urn:xmpp:message-retract:0'/>
...
</query>
</iq>]]></example>
</section1>
<section1 topic='Use Case' anchor='usecase'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>Consider a situation where a user sends a message to the wrong recipient: </p>
<example caption="The user's client sends a message to the wrong recipient"><![CDATA[
<message type='chat' to='lord@capulet.example' id='wrong-recipient-1'>
<body>Have not saints lips, and holy palmers too?</body>
<origin-id xmlns='urn:xmpp:sid:0' id='origin-id-1'/>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</message>]]></example>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>The message author notices that the message was sent to the wrong recipient and indicates to their client that the message should be retracted.</p>
<p>The client sends out a retraction message which uses &xep0422; to indicate that it applies to the wrongly sent message by referring to its XEP-0359 origin ID.</p>
<example caption="The client sends out a retraction message"><![CDATA[
<message type='chat' to='lord@capulet.example' id='retract-message-1'>
<apply-to id="origin-id-1" xmlns="urn:xmpp:fasten:0">
<retract xmlns='urn:xmpp:message-retract:0'/>
</apply-to>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</message>]]></example>
</section1>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<section1 topic='Tombstones' anchor='tombstones'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>An archiving service MAY replace a retracted message with a 'tombstone' recording the fact that the message was retracted (but otherwise preserving the fact that the message did once exist in order to aid synchronizing archives). The message gets replaced with a &lt;retracted/&gt; element which SHOULD include a 'by' attribute specifying the JID of the entity that sent the retraction and a 'stamp' attribute indicating the time at which the retraction took place.</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<example caption='Retracted message tombstone in a MAM result'><![CDATA[
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<message id='aeb213' to='lord@capulet.example/chamber'>
<result xmlns='urn:xmpp:mam:2' queryid='f27' id='28482-98726-73623'>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<forwarded xmlns='urn:xmpp:forward:0'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<delay xmlns='urn:xmpp:delay' stamp='2019-09-20T23:08:25Z'/>
<retracted by="romeo@montague.example" stamp='2019-09-20T23:09:32Z' xmlns='urn:xmpp:message-retract:0' />
</forwarded>
</result>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</message>]]></example>
</section1>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<section1 topic='Business Rules' anchor='rules'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>A receiving client can choose to remove the retracted message from whatever display is used for messages, from any stored history, or choose to display the fact that a message has been retracted in another way.</p>
<p>A MUC or other service that supports message retraction SHOULD prevent further distribution of the message by the service (e.g., by not replaying the message to new occupants joiningthe room, omitting the message from history archive requests where possible, or replacing the original message with a 'tombstone').</p>
<p>Some clients may have been offline while the retraction was issued. The archiving service therefore MUST store the retraction message, regardless of whether the original message is deleted or replaced with a tombstone. These clients will then become aware of the retraction as soon as they catch up with the archive.</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<p>A client MAY inform the user that a no-longer displayed message did previously exist and has been removed.</p>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>Clients MUST set the XEP-0359 'origin id' attribute on sent messages to make them suitable for message retraction.</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<p>The Sender MUST NOT send a retraction request for a message with non-messaging payloads. For example, a sender MUST NOT send a retraction for a roster item exchange request or a file transfer part.</p>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>A retraction (that's not part of a protoXEP message moderation operation) MUST only be processed when both the original message and the retraction request are received from the same bare-JID (in a one-on-one conversation) or full-JID (in a non-anonymous MUC from &xep0045;).</p>
<p>When used in a semi-anonymous MUC, the recipient client MUST check that a message retraction was sent by the author of the retracted message by checking the occupant id from &xep0421;.</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>There can never be a guarantee that a retracted message was never seen or otherwise distributed, and it is encouraged for clients and services when possible to inform users that no such guarantee exists.</p>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<p>To prevent message spoofing, it's very important that the JID or occupant id of message retractions are checked (as explained in the <link url='#rules'>Business Rules</link> section).</p>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>None.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>The &REGISTRAR; includes 'urn:xmpp:message-retract:0' in its registry of protocol namespaces (see &NAMESPACES;).</p>
<ul>
<li>urn:xmpp:message-retract:0</li>
</ul>
</section2>
<section2 topic='Protocol Versioning' anchor='registrar-versioning'>
&NSVER;
</section2>
</section1>
<section1 topic='XML Schema' anchor='schema'>
<code><![CDATA[
<?xml version='1.0' encoding='UTF-8'?>
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='urn:xmpp:message-retract:0'
xmlns='urn:xmpp:message-retract:0'
elementFormDefault='qualified'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<xs:element name='retract'></xs:element>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
<xs:element name='retracted'>
<xs:complexType>
<xs:simpleContent>
<xs:extension base='xs:string'>
Update message retractions protoXEP * The MUC moderation use-case will be split out into a different XEP * Update this XEP to handle the case where a user retracts their own message * Use XEP-0422 for the retraction message * Mention in security considerations that the XEP-0421 occupant id must be checked
2019-09-24 05:55:00 -04:00
<xs:attribute name='by' type='xs:string' use='required'/>
<xs:attribute name='from' type='xs:string' use='optional'/>
<xs:attribute name='stamp' type='xs:dateTime' use='required'/>
Update message deletion protoxep based on Council feedback
2016-10-12 13:30:54 -04:00
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:schema>
]]></code>
</section1>
</xep>
Reference in New Issue Copy Permalink