moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

XEP-0280: Restructure Section 9: Avoiding Carbon for single msg

This commit is contained in:
Stefan Haun 2017-02-10 21:57:24 +01:00 committed by Sam Whited
parent 5e93c5b665
commit 549d4fb9f4
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
xep-0280.xml
View File

@ -350,15 +350,19 @@
<p>
Some clients might want to avoid Carbons on a single message, while still
keeping all of the other semantics of Carbon support.
This might be useful for clients sending end-to-end encrypted messages, for
example.
The sending client MAY exclude a &MESSAGE; from being forwarded to other
Carbons-enabled resources, by adding a &lt;private/&gt; element qualified by
the namespace "urn:xmpp:carbons:2" and a &lt;no-copy/&gt; hint as described
in &xep0334; as child elements of the &MESSAGE; stanza.
This might be useful for clients sending end-to-end encrypted messages.
</p>
<p><strong>Note:</strong> use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.</p>
<ul>
<li> The sending client MAY exclude a &MESSAGE; from being forwarded to other Carbons-enabled resources, by adding a &lt;private/&gt; element qualified by the namespace "urn:xmpp:carbons:2" and a &lt;no-copy/&gt; hint as described in &xep0334; as child elements of the &MESSAGE; stanza.</li>
<li>The sending server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resources of the sender.</li>
<li>The receiving server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resource of the recipient,</li>
<li>and the receiving server SHOULD remove the &lt;private/&gt; element before delivering to the recipient.</li>
</ul>
<p><strong>Note:</strong>
Use of the private mechanism might lead to partial conversations on other devices. This is the intended effect.
If the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to <cite>RFC 6121</cite>. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the &lt;private/&gt; element for recipients.</p>
<example caption='Romeo sends to Juliet, excluding Carbons'><![CDATA[
<message xmlns='jabber:client'
@ -381,8 +385,6 @@
<private xmlns='urn:xmpp:carbons:2'/>
<no-copy xmlns='urn:xmpp:hints'/>
</message>]]></example>
<p>The sending server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resources of the sender. The receiving server MUST NOT deliver forwarded &MESSAGE;s to the other Carbons-enabled resource of the recipient, and SHOULD remove the &lt;private/&gt; element before delivering to the recipient.</p>
<p><strong>Note:</strong> if the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to <cite>RFC 6121</cite>. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the &lt;private/&gt; element for recipients.</p>
</section1>
<section1 topic='Business Rules' anchor='bizrules'>
<section2 topic='Handling Multiple Enable/Disable Requests' anchor='bizrules-multi'>